From: Andrew Morton <akpm@linux-foundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
hpa@zytor.com, jeremy.fitzhardinge@citrix.com, mingo@redhat.com,
stable@kernel.org, tglx@linutronix.de
Subject: Re: Not really merged? Re: [merged] x86-paravirt-pte-updates-in-kunmap_atomic-need-to-be-synchronous-regardless-of-lazy_mmu-mode.patch removed from -mm tree
Date: Thu, 27 Oct 2011 15:53:29 -0700 [thread overview]
Message-ID: <20111027155329.0adc1358.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111025182450.GA9843@phenom.dumpdata.com>
On Tue, 25 Oct 2011 14:24:50 -0400
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Fri, Oct 14, 2011 at 12:51:48PM -0700, akpm@google.com wrote:
> >
> > The patch titled
> > Subject: x86/paravirt: PTE updates in k(un)map_atomic need to be synchronous, regardless of lazy_mmu mode
> > has been removed from the -mm tree. Its filename was
> > x86-paravirt-pte-updates-in-kunmap_atomic-need-to-be-synchronous-regardless-of-lazy_mmu-mode.patch
> >
> > This patch was dropped because it was merged into mainline or a subsystem tree
>
> Hey Andrew,
>
> I am actually not seeing this in mainline? Was it accidently dropped out of your tree?
hm, well spotted. I'm not sure what happened here - possibly the patch
was merged into an x86 tree (and hence linux-next) but later got lost.
Or possibly not, and I just screwed up.
Either way, it's a pretty important patch - we marked it for -stable
backporting.
> If that is the case I can convience you to put it back in or can I drive it to Linus with
> your Ack-ed by?
I resurrected my copy and shall send it along to the x86 guys soon.
next prev parent reply other threads:[~2011-10-27 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201110141951.p9EJpn3A006989@hpaq5.eem.corp.google.com>
2011-10-25 18:24 ` Konrad Rzeszutek Wilk
2011-10-27 22:53 ` Andrew Morton [this message]
2011-10-28 7:08 ` Ingo Molnar
2011-10-28 7:39 ` Andrew Morton
2011-10-28 7:48 ` [Xen tree maintenance] " Ingo Molnar
2011-10-28 13:59 ` Konrad Rzeszutek Wilk
2011-10-28 14:33 ` Konrad Rzeszutek Wilk
2011-11-30 11:02 ` Stefan Bader
2011-11-30 19:41 ` Andrew Morton
2011-12-05 15:56 ` Ingo Molnar
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=20111027155329.0adc1358.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome