From: Andrew Morton <akpm@linux-foundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"namhyung@gmail.com" <namhyung@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
David Vrabel <david.vrabel@citrix.com>,
"rientjes@google.com" <rientjes@google.com>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>
Subject: Re: [Xen-devel] Re: [Revert] Re: [PATCH] mm: sync vmalloc address space page tables in alloc_vm_area()
Date: Tue, 8 Nov 2011 15:36:35 -0800 [thread overview]
Message-ID: <20111108153635.45b3c517.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111108233132.GA1230@phenom.dumpdata.com>
On Tue, 8 Nov 2011 18:31:32 -0500
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > > And Linus picked it up.
> >
> > I've no idea what's going on here.
>
> Heh. Sorry for being so confusing. Merge windows are a bit stressful and
> I sometimes end up writing run-on sentences.
> >
> > > .. snip..
> > > >
> > > > Also, not sure what you thought of this patch below?
> > >
> > > Patch included as attachment for easier review..
> >
> > The patch "xen: map foreign pages for shared rings by updating the PTEs
> > directly" (whcih looks harnless enough) is not present in 3.2-rc1 or linux-next.
>
> <nods>. That is b/c it does not have your Ack. The patch applies cleanly to
> 3.2-rc1 (as all the other patches that it depends on are now in 3.2-rc1).
>
> I am humbly asking for you to:
> a) review the patch (which you did) and get an idea whether you are OK (sounds like you are)
Yup.
> b) pick it up in your -mm tree.
No added benefit there.
> or alternately:
> b) give an Ack on the patch so I can put it in my linux-next and push it
> for 3.2-rc1.
That's OK by me.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-08 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1314877863-21977-1-git-send-email-david.vrabel@citrix.com>
2011-09-01 16:11 ` [Revert] Re: [PATCH] mm: sync vmalloc address space page tables in alloc_vm_area() Konrad Rzeszutek Wilk
2011-09-01 20:37 ` Jeremy Fitzhardinge
2011-09-01 21:17 ` Andrew Morton
2011-09-02 11:39 ` David Vrabel
2011-09-02 22:32 ` Andrew Morton
2011-09-02 23:04 ` Jeremy Fitzhardinge
2011-09-06 16:35 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-11-05 13:38 ` Konrad Rzeszutek Wilk
2011-11-07 20:36 ` Konrad Rzeszutek Wilk
2011-11-08 23:01 ` Andrew Morton
2011-11-08 23:31 ` Konrad Rzeszutek Wilk
2011-11-08 23:36 ` Andrew Morton [this message]
2011-09-02 7:22 ` Ian Campbell
2011-09-02 7:31 ` Keir Fraser
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=20111108153635.45b3c517.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david.vrabel@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=namhyung@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rientjes@google.com \
--cc=xen-devel@lists.xensource.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).