From: Chris Wright <chrisw@sous-sol.org>
To: linux-kernel@vger.kernel.org, stable@kernel.org
Cc: Justin Forbes <jmforbes@linuxtx.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
Dave Jones <davej@redhat.com>,
Chuck Wolber <chuckw@quantumlinux.com>,
torvalds@osdl.org, akpm@osdl.org, alan@lxorguk.ukuu.org.uk
Subject: [PATCH 0/4] -stable review
Date: Thu, 02 Mar 2006 23:55:42 -0800 [thread overview]
Message-ID: <20060303075542.659414000@sorel.sous-sol.org> (raw)
This is the start of the stable review cycle for the 2.6.15.6 release.
There are 4 patches in this series, 2 of which are simply compile fixes
for the problems with 2.6.15.5, 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 Sun Mar 5 08:00 UTC. Anything received
after that time, might be too late.
thanks,
the -stable release team
--
next reply other threads:[~2006-03-03 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 7:55 Chris Wright [this message]
2006-03-03 7:55 ` [PATCH 1/4] [REQSK] Dont reset rskq_defer_accept in reqsk_queue_alloc Chris Wright
2006-03-03 7:55 ` [PATCH 2/4] [PATCH] [IA64] die_if_kernel() can return (CVE-2006-0742) Chris Wright
2006-03-03 7:55 ` [PATCH 3/4] [PATCH] fs/nfs/direct.c compile fix Chris Wright
2006-03-03 7:55 ` [PATCH 4/4] [PATCH] mempolicy.c compile fix, make sure BITS_PER_BYTE is defined Chris Wright
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=20060303075542.659414000@sorel.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chuckw@quantumlinux.com \
--cc=davej@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®