From: Greg KH
Date: Mon Jan 18 2010 - 13:50:44 EST

I'm announcing the release of the kernel. All users of the
.31 kernel series are strongly encouraged to upgrade.

No, forget that, all users of the .31 kernel series as released by the
-stable team should move to the .32 kernel series as soon as possible.

This is the last .31 kernel release barring something really odd
happening, so please, everyone move to .32 now, I do not know of any
reason you should stick with .31 at this point in time.

The updated 2.6.31.y git tree can be found at:
and can be browsed at the normal git web browser:;a=summary


greg k-h


Makefile | 2
drivers/acpi/sleep.c | 40 +++++++++++++++
drivers/hwmon/adt7462.c | 2
fs/fcntl.c | 102 +++++++++++++++++++++++++--------------
fs/quota/dquot.c | 3 +
kernel/audit_tree.c | 13 +++-
kernel/signal.c | 3 -
net/bridge/netfilter/ebtables.c | 6 ++
net/ipv6/exthdrs.c | 7 ++
net/netfilter/nf_conntrack_ftp.c | 18 +++---
10 files changed, 142 insertions(+), 54 deletions(-)

Al Viro (2):
fix braindamage in audit_tree.c untag_chunk()
fix more leaks in audit_tree.c tag_chunk()

Andi Kleen (1):
kernel/signal.c: fix kernel information leak with print-fatal-signals=1

David S. Miller (1):
ipv6: skb_dst() can be NULL in ipv6_hop_jumbo().

Florian Westphal (1):
netfilter: ebtables: enforce CAP_NET_ADMIN

Greg Kroah-Hartman (1):

Gustavo Maciel Dias Vieira (1):
ACPI: add DMI entry for SCI_EN resume quirk on HP dv4

Jan Kara (1):
quota: Fix dquot_transfer for filesystems different from ext4

Len Brown (2):
ACPI: sleep: another HP DMI entry for init_set_sci_en_on_resume
ACPI: DMI init_set_sci_en_on_resume for HP-Compaq C700

Linus Torvalds (1):
fasync: split 'fasync_helper()' into separate add/remove functions

Patrick McHardy (1):
netfilter: nf_ct_ftp: fix out of bounds read in update_nl_seq()

Roger Blofeld (1):
hwmon: (adt7462) Fix pin 28 monitoring

Vaibhav Verma (1):
ACPI: sleep: another HP/Compaq DMI entries for init_set_sci_en_on_resume

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at