From: Greg KH <greg@kroah.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jan Beulich <JBeulich@suse.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Put git commit 51ac8893a7a51b196501164e645583bf78138699 on the stable tree please
Date: Fri, 22 Feb 2013 09:07:42 -0800 [thread overview]
Message-ID: <20130222170742.GA5126@kroah.com> (raw)
In-Reply-To: <5127AED302000078000C0779@nat28.tlf.novell.com> <20130222165704.GA21811@phenom.dumpdata.com>
On Fri, Feb 22, 2013 at 11:57:04AM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 22, 2013 at 08:19:30AM -0800, Greg KH wrote:
> > On Fri, Feb 22, 2013 at 10:46:45AM -0500, Konrad Rzeszutek Wilk wrote:
> > > Hey Greg,
> > >
> > > Please put git commit 51ac8893a7a51b196501164e645583bf78138699
> > > commit 51ac8893a7a51b196501164e645583bf78138699
> > > Author: Jan Beulich <jbeulich@suse.com>
> > > Date: Wed Feb 6 10:30:38 2013 -0500
> > >
> > > xen-pciback: rate limit error messages from xen_pcibk_enable_msi{,x}()
> > >
> > > on the stable tree please. It is an security errata fix and should
> > > have had the CC: stable@vger.kernel.org but did not.
> >
> > Thanks, what stable kernel releases should it be queued up for?
>
> 3.4 and later please.
On Fri, Feb 22, 2013 at 04:45:55PM +0000, Jan Beulich wrote:
> Anyone from 3.1 onwards that is still being maintained.
Hm, who should I believe here... :)
It doesn't matter for me, but for the 3.2 tree, it does.
thanks,
greg k-h
next prev parent reply other threads:[~2013-02-22 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 15:46 Put git commit 51ac8893a7a51b196501164e645583bf78138699 on the stable tree please Konrad Rzeszutek Wilk
2013-02-22 16:19 ` Greg KH
2013-02-22 16:45 ` Jan Beulich
2013-02-22 17:03 ` Konrad Rzeszutek Wilk
2013-02-22 16:57 ` Konrad Rzeszutek Wilk
2013-02-22 17:07 ` Greg KH [this message]
2013-02-25 16:46 ` Konrad Rzeszutek Wilk
2013-03-02 22:33 ` Ben Hutchings
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=20130222170742.GA5126@kroah.com \
--to=greg@kroah.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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