public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: kevin.tian@intel.com, dkiper@net-space.pl,
	Rzeszutek@dumpdata.com, Wilk@dumpdata.com, stable@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [stable] [PATCH] Xen bug-fixes for 2.6.39 (already in 2.6.40)
Date: Mon, 30 May 2011 17:40:46 +0800	[thread overview]
Message-ID: <20110530094046.GF11601@kroah.com> (raw)
In-Reply-To: <20110526123921.GB3386@dumpdata.com>

On Thu, May 26, 2011 at 08:39:21AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, May 26, 2011 at 12:02:39AM -0700, Greg KH wrote:
> > On Wed, May 25, 2011 at 05:37:32PM -0400, Konrad@dumpdata.com wrote:
> > > Hey stable-tree maintainer(s).
> > > 
> > > The follow four patches are in the 2.6.40 tree and should be back-ported to 2.6.39 (only).
> > > I forgot to CC:stable on them, so manually doing it here.
> > > 
> > > The four patches in question have the following git commits:
> > > 
> > > 8c5950881c3b5e6e350e4b0438a8ccc513d90df9
> > >     xen/p2m: Create entries in the P2M_MFN trees's to track 1-1 mappings
> > > 0f16d0dfcdb5aab97d9e368f008b070b5b3ec6d3
> > >     xen/setup: Fix for incorrect xen_extra_mem_start initialization under 32-bit
> > > 15bfc094517db2ddf38ca7ed47f3a1c0ad24f7c4
> > >     xen/setup: Ignore E820_UNUSABLE when setting 1-1 mappings.
> > > 7899891c7d161752f29abcc9bc0a9c6c3a3af26c
> > >     xen mmu: fix a race window causing leave_mm BUG()
> > > 
> > > And are part of this email chain. Please apply them to 2.6.39.1 tree.
> > 
> > I need an ack from the Xen maintainer and the original patch author
> > before I can accept these.  Please get them to provide this and I will
> 
> OK
> 
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> (who is the Xen maintainer)
> 
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> (who is also the original patch author on some of the patches)

Thanks, as you didn't send the original request from your maintainer
address, how was I to know that you were the same Konrad Rzeszutek Wilk?  :)

thanks,

greg k-h

  parent reply	other threads:[~2011-05-30  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 21:37 [PATCH] Xen bug-fixes for 2.6.39 (already in 2.6.40) Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH] xen mmu: fix a race window causing leave_mm BUG() Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH] xen/p2m: Create entries in the P2M_MFN trees's to track 1-1 mappings Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH 1/2] xen/setup: Ignore E820_UNUSABLE when setting " Konrad, Rzeszutek, Wilk
2011-05-25 21:37 ` [PATCH 2/2] xen/setup: Fix for incorrect xen_extra_mem_start initialization under 32-bit Konrad, Rzeszutek, Wilk
2011-05-26  7:02 ` [stable] [PATCH] Xen bug-fixes for 2.6.39 (already in 2.6.40) Greg KH
2011-05-26 12:39   ` Konrad Rzeszutek Wilk
2011-05-26 12:44     ` Tian, Kevin
2011-05-26 13:14     ` Daniel Kiper
2011-05-30  9:40     ` Greg KH [this message]
2011-05-31 14:26       ` Konrad Rzeszutek Wilk

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=20110530094046.GF11601@kroah.com \
    --to=greg@kroah.com \
    --cc=Rzeszutek@dumpdata.com \
    --cc=Wilk@dumpdata.com \
    --cc=dkiper@net-space.pl \
    --cc=kevin.tian@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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