From: Chris Wright <chrisw@sous-sol.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
netdev@vger.kernel.org,
linux kernel <linux-kernel@vger.kernel.org>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [stable] [PATCH] alloc_percpu() fails to allocate percpu data
Date: Tue, 11 Mar 2008 17:18:13 -0700 [thread overview]
Message-ID: <20080312001813.GS4416@sequoia.sous-sol.org> (raw)
In-Reply-To: <170fa0d20803111239u4d25b7c8p915e63a43cb389c6@mail.gmail.com>
* Mike Snitzer (snitzer@gmail.com) wrote:
> On 3/11/08, Eric Dumazet <dada1@cosmosbay.com> wrote:
> > Mike Snitzer a écrit :
> > > I see that this fix was committed to mainline as commit
> > > be852795e1c8d3829ddf3cb1ce806113611fa555
> > >
> > > The commit didn't "Cc: <stable@kernel.org>", and it doesn't appear to
> > > be queued for 2.6.24.x. Should it be?
> >
> > Yes, it should be queued fo 2.6.24.x
>
> That means both of the following commits need to be cherry-picked into 2.6.24.x:
> b3242151906372f30f57feaa43b4cac96a23edb1
> be852795e1c8d3829ddf3cb1ce806113611fa555
Just send each with appropriate commit hash id and relevant Cc's to
stable@kernel.org so we can pick them up.
thanks,
-chris
prev parent reply other threads:[~2008-03-12 0:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:00 [PATCH] alloc_percpu() fails to allocate percpu data Eric Dumazet
2008-02-21 22:26 ` Peter Zijlstra
2008-02-23 9:23 ` Nick Piggin
2008-02-27 19:44 ` Christoph Lameter
2008-03-03 3:14 ` Nick Piggin
2008-03-03 7:48 ` Eric Dumazet
2008-03-03 9:41 ` Nick Piggin
2008-03-03 19:30 ` Christoph Lameter
2008-02-23 8:04 ` Andrew Morton
2008-02-27 19:59 ` Christoph Lameter
2008-02-27 20:24 ` Andrew Morton
2008-02-27 21:56 ` Christoph Lameter
2008-03-01 13:53 ` Eric Dumazet
2008-03-11 18:15 ` Mike Snitzer
2008-03-11 18:41 ` Eric Dumazet
2008-03-11 19:39 ` Mike Snitzer
2008-03-12 0:18 ` Chris Wright [this message]
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=20080312001813.GS4416@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=snitzer@gmail.com \
--cc=stable@kernel.org \
--cc=yanmin_zhang@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).