From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Linux-Arch <linux-arch@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Hugh Dickins <hugh@tiscali.co.uk>,
linux-kernel@vger.kernel.org,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()
Date: Wed, 22 Jul 2009 19:59:08 -0500 [thread overview]
Message-ID: <74BA64FD-0DFF-45A2-868D-A001D9BA496F@kernel.crashing.org> (raw)
In-Reply-To: <1248310415.3367.22.camel@pasglop>
On Jul 22, 2009, at 7:53 PM, Benjamin Herrenschmidt wrote:
> On Wed, 2009-07-22 at 09:31 -0700, Linus Torvalds wrote:
>>> CC'ing Linus here. How do you want to proceed with that merge ?
>>> (IE. so
>>> far nobody objected to the patch itself)
>>
>> Maybe you can put it as a separate branch in -next, and have it
>> merged
>> before the stuff that depends on it, and then just sending it to me
>> (as a
>> git branch or patch or whatever) in the first day of the merge
>> window?
>
> Hrm... my powerpc-next branch will contain stuff that depend on it, so
> I'll probably have to pull it in though, unless I tell all my
> sub-maintainers to also pull from that other branch first :-)
Can you not cherry pick it into powerpc-next to 'pull it through'?
- k
next prev parent reply other threads:[~2009-07-23 0:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:49 Benjamin Herrenschmidt
2009-07-15 13:56 ` Nick Piggin
2009-07-16 1:54 ` Benjamin Herrenschmidt
2009-07-20 8:10 ` Nick Piggin
2009-07-20 10:00 ` Benjamin Herrenschmidt
2009-07-20 10:38 ` Nick Piggin
2009-07-21 0:02 ` Benjamin Herrenschmidt
2009-07-21 7:05 ` Nick Piggin
2009-07-20 7:11 ` Benjamin Herrenschmidt
2009-07-20 7:48 ` Martin Schwidefsky
2009-07-20 8:05 ` Nick Piggin
2009-07-20 9:59 ` Benjamin Herrenschmidt
2009-07-20 10:39 ` Nick Piggin
2009-07-22 16:31 ` Linus Torvalds
2009-07-23 0:53 ` Benjamin Herrenschmidt
2009-07-23 0:59 ` Kumar Gala [this message]
2009-07-27 19:11 ` Linus Torvalds
2009-07-27 21:35 ` Benjamin Herrenschmidt
2009-07-28 0:17 ` Benjamin Herrenschmidt
2009-07-28 0:25 ` Paul Mundt
2009-07-28 0:41 ` Linus Torvalds
2009-07-16 1:36 ` Michael Ellerman
2009-07-16 1:56 ` Benjamin Herrenschmidt
2009-07-20 12:46 ` David Howells
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=74BA64FD-0DFF-45A2-868D-A001D9BA496F@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=hugh@tiscali.co.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®