public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org, stable@kernel.org
Cc: stable-review@kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk
Subject: [patch 0/8] 2.6.27.27-stable review
Date: Fri, 17 Jul 2009 13:39:35 -0700	[thread overview]
Message-ID: <20090717203935.GA5641@kroah.com> (raw)

This is the start of the stable review cycle for the 2.6.27.27 release.
There are 8 patches in this series, all will be posted as a response to
this one.  If anyone has any issues with these being applied, please let
us know.  If anyone is a maintainer of the proper subsystem, and wants
to add a Signed-off-by: line to the patch, please respond with it.

These patches are sent out with a number of different people on the Cc:
line.  If you wish to be a reviewer, please email stable@kernel.org to
add your name to the list.  If you want to be off the reviewer list,
also email us.

Responses should be made by Sunday July 19, 20:00:00 UTC UTC.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
	kernel.org/pub/linux/kernel/v2.6/stable-review/patch-2.6.27.27-rc1.gz
and the diffstat can be found below.


thanks,

greg k-h


 Makefile                      |    7 ++-
 drivers/block/floppy.c        |    5 ++-
 drivers/net/tulip/interrupt.c |   84 +++++++++++++++++++++++++++--------------
 drivers/net/tulip/tulip.h     |   32 +++++++++++++++-
 drivers/pci/iova.c            |   26 +++++++++++--
 include/linux/mm.h            |    2 -
 include/linux/personality.h   |    5 ++-
 include/linux/security.h      |    2 +
 kernel/resource.c             |    2 +-
 kernel/sysctl.c               |    2 -
 mm/Kconfig                    |   18 +++++++++
 mm/mmap.c                     |    3 +
 security/Kconfig              |   22 +----------
 security/security.c           |    3 -
 14 files changed, 145 insertions(+), 68 deletions(-)

             reply	other threads:[~2009-07-17 20:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090717203718.637372453@mini.kroah.org>
2009-07-17 20:39 ` Greg KH [this message]
2009-07-17 20:37   ` [patch 1/8] Add -fno-delete-null-pointer-checks to gcc CFLAGS Greg KH
2009-07-17 20:37   ` [patch 2/8] personality: fix PER_CLEAR_ON_SETID (CVE-2009-1895) Greg KH
2009-07-17 20:37   ` [patch 3/8] security: use mmap_min_addr indepedently of security models Greg KH
2009-07-17 20:37   ` [patch 4/8] Fix iommu address space allocation Greg KH
2009-07-17 20:37   ` [patch 5/8] floppy: fix lock imbalance Greg KH
2009-07-17 20:37   ` [patch 6/8] kernel/resource.c: fix sign extension in reserve_setup() Greg KH
2009-07-17 20:37   ` [patch 7/8] tulip: Fix for MTU problems with 802.1q tagged frames Greg KH
2009-07-17 20:37   ` [patch 8/8] Dont use -fwrapv compiler option: its buggy in gcc-4.1.x Greg KH
     [not found]   ` <200907180329.34323.arekm@maven.pl>
2009-07-20  3:48     ` [patch 0/8] 2.6.27.27-stable review Greg KH
2009-07-18  6:44 Ozkan Sezer
2009-07-18  8:35 ` Stefan Richter

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=20090717203935.GA5641@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-review@kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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