public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.6.16.51
Date: Wed, 9 May 2007 06:42:47 +0200	[thread overview]
Message-ID: <20070509044247.GK4226@stusta.de> (raw)

Location:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/

git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git

RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=rss


Changes since 2.6.16.50:

Adrian Bunk (3):
      x86_64: ACPI_CPU_FREQ must select CPU_FREQ_TABLE
      Linux 2.6.16.51-rc1
      Linux 2.6.16.51

Andrew Hendry (1):
      [X.25]: Add missing sock_put in x25_receive_data

Hugh Dickins (4):
      holepunch: fix shmem_truncate_range punching too far
      holepunch: fix shmem_truncate_range punch locking
      holepunch: fix disconnected pages after second truncate
      holepunch: fix mmap_sem i_mutex deadlock

Jaroslav Kysela (1):
      [NETFILTER]: ipt_CLUSTERIP: fix oops in checkentry function

Jean Delvare (1):
      hwmon/w83627ehf: Don't redefine REGION_OFFSET

Jorge Boncompte (1):
      [NETFILTER]: ip_nat_proto_gre: do not modify/corrupt GREv0 packets through NAT


 Makefile                                              |    2 
 arch/x86_64/kernel/cpufreq/Kconfig                    |    1 
 drivers/hwmon/w83627ehf.c                             |   14 -
 include/linux/netfilter_ipv4/ip_conntrack_proto_gre.h |   19 -
 mm/madvise.c                                          |   19 +
 mm/shmem.c                                            |  132 +++++++---
 net/ipv4/netfilter/ip_nat_proto_gre.c                 |   21 -
 net/ipv4/netfilter/ipt_CLUSTERIP.c                    |    2 
 net/x25/x25_dev.c                                     |    1 
 9 files changed, 132 insertions(+), 79 deletions(-)


                 reply	other threads:[~2007-05-09  4:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070509044247.GK4226@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox