Re: [PATCH] increment hpilo version
From: Andrew Morton
Date: Mon Feb 02 2009 - 15:14:32 EST
On Mon, 02 Feb 2009 14:56:18 -0500
Jeff Mahoney <jeffm@xxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> David Altobelli wrote:
> > Bump hpilo module version to indicate that the open/close bug is fixed.
>
> Hi David -
>
> Was the open/close bug fixed in a differently than with your patch in
> "[PATCH] hpilo open/close fix" ? If not, the fix didn't make it into
> mainline, but this version bump did.
I'll be sending hpilo-open-close-fix.patch in the next batch, this week
some time.
If you grab http://userweb.kernel.org/~akpm/mmotm/series you can see
what I have queued for 2.6.29. Look for
#
# 2.6.29 queue:
#
and
#
# more 2.6.29 queue:
#
The first is soon-to-go stuff, the second is
to-go-after-a-bit-more-baking stuff.
Also,
#
# others:
#
is stuff which I think might be needed in 2.6.29 but which go via
subsystem maintainers trees.
The latter is not (yet) as lengthy as usual, but there's still quite a
bit of material:
acpi-kconfig-fix-acpi_container-module-name.patch
acpi-dock-dont-eval-_sta-on-every-show_docked-sysfs-read.patch
arm-at91-fix-nr_aic_irqs-undeclared.patch
drivers-ata-sata_silc-needs-dmih.patch
pata_amd-program-fifo.patch
pata_legacy-for-vlb-32bit-pio-dont-try-tricks-with-slop.patch
mfd-initialise-wm8350-interrupts-earlier.patch
mfd-mark-wm835x-usb_slv_500ma-bit-as-accessible.patch
mfd-pcf50633-terminate-i2c_device_id-list.patch
mtd-physmap-fix-wrong-free-and-del_mtd_partitiondevice.patch
net-dont-use-in_atomic-in-gfp_any.patch
documentation-connector-cn_testc-dont-use-gfp_any.patch
nommu-fix-a-number-of-issues-with-the-per-mm-vma-patch.patch
powerpc-fix-code-for-reserved-memory-spanning-across-nodes.patch
atmel_serial-might-lose-modem-status-change.patch
pipe_rdwr_fasync-fix-the-error-handling-to-prevent-the-leak-crash.patch
xtensa-fix-compilation-somewhat.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/