All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Hugh Dickins <hugh@tiscali.co.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()
Date: Mon, 20 Jul 2009 19:59:21 +1000	[thread overview]
Message-ID: <1248083961.30899.5.camel@pasglop> (raw)
In-Reply-To: <20090720080502.GG7298@wotan.suse.de>

On Mon, 2009-07-20 at 10:05 +0200, Nick Piggin wrote:
> 
> Unless anybody has other preferences, just send it straight to Linus in
> the next merge window -- if any conflicts did come up anyway they would
> be trivial. You could just check against linux-next before doing so, and
> should see if it is going to cause problems for any arch pull...

Well, the problem is that powerpc-next will need that patch, which means
that if I don't put it in my tree, Steven won't be able to build
powerpc-next as part of linux-next until the patch is merged. Hence my
question, what's the best way to handle that :-) There isn't an mm-next
is there ? If there was, I could tell Steven to always pull powerpc
after mm for example. Or I can put it in a git tree of its own with a
dependency for Steven to pull.

Cheers,
Ben.

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Hugh Dickins <hugh@tiscali.co.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()
Date: Mon, 20 Jul 2009 19:59:21 +1000	[thread overview]
Message-ID: <1248083961.30899.5.camel@pasglop> (raw)
Message-ID: <20090720095921.VQV28x5UtC3-NMPsQY0SDJdPC9keBAuVgFG1rZhPCiE@z> (raw)
In-Reply-To: <20090720080502.GG7298@wotan.suse.de>

On Mon, 2009-07-20 at 10:05 +0200, Nick Piggin wrote:
> 
> Unless anybody has other preferences, just send it straight to Linus in
> the next merge window -- if any conflicts did come up anyway they would
> be trivial. You could just check against linux-next before doing so, and
> should see if it is going to cause problems for any arch pull...

Well, the problem is that powerpc-next will need that patch, which means
that if I don't put it in my tree, Steven won't be able to build
powerpc-next as part of linux-next until the patch is merged. Hence my
question, what's the best way to handle that :-) There isn't an mm-next
is there ? If there was, I could tell Steven to always pull powerpc
after mm for example. Or I can put it in a git tree of its own with a
dependency for Steven to pull.

Cheers,
Ben.


WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: 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>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()
Date: Mon, 20 Jul 2009 19:59:21 +1000	[thread overview]
Message-ID: <1248083961.30899.5.camel@pasglop> (raw)
In-Reply-To: <20090720080502.GG7298@wotan.suse.de>

On Mon, 2009-07-20 at 10:05 +0200, Nick Piggin wrote:
> 
> Unless anybody has other preferences, just send it straight to Linus in
> the next merge window -- if any conflicts did come up anyway they would
> be trivial. You could just check against linux-next before doing so, and
> should see if it is going to cause problems for any arch pull...

Well, the problem is that powerpc-next will need that patch, which means
that if I don't put it in my tree, Steven won't be able to build
powerpc-next as part of linux-next until the patch is merged. Hence my
question, what's the best way to handle that :-) There isn't an mm-next
is there ? If there was, I could tell Steven to always pull powerpc
after mm for example. Or I can put it in a git tree of its own with a
dependency for Steven to pull.

Cheers,
Ben.

  reply	other threads:[~2009-07-20  9:59 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  7:49 [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Benjamin Herrenschmidt
2009-07-15  7:49 ` Benjamin Herrenschmidt
2009-07-15  7:49 ` Benjamin Herrenschmidt
2009-07-15  7:49 ` Benjamin Herrenschmidt
2009-07-15 13:56 ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-15 13:56   ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Nick Piggin
2009-07-15 13:56   ` Nick Piggin
2009-07-16  1:54   ` Benjamin Herrenschmidt
2009-07-16  1:54     ` Benjamin Herrenschmidt
2009-07-16  1:54     ` Benjamin Herrenschmidt
2009-07-20  8:10     ` Nick Piggin
2009-07-20  8:10       ` Nick Piggin
2009-07-20  8:10       ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-20 10:00       ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Benjamin Herrenschmidt
2009-07-20 10:00         ` Benjamin Herrenschmidt
2009-07-20 10:00         ` Benjamin Herrenschmidt
2009-07-20 10:38         ` Nick Piggin
2009-07-20 10:38           ` Nick Piggin
2009-07-20 10:38           ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-21  0:02           ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Benjamin Herrenschmidt
2009-07-21  0:02             ` Benjamin Herrenschmidt
2009-07-21  0:02             ` Benjamin Herrenschmidt
2009-07-21  7:05             ` Nick Piggin
2009-07-21  7:05               ` Nick Piggin
2009-07-21  7:05               ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-20  7:11   ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Benjamin Herrenschmidt
2009-07-20  7:11     ` Benjamin Herrenschmidt
2009-07-20  7:11     ` Benjamin Herrenschmidt
2009-07-20  7:48     ` Martin Schwidefsky
2009-07-20  7:48       ` Martin Schwidefsky
2009-07-20  7:48       ` Martin Schwidefsky
2009-07-20  8:05     ` Nick Piggin
2009-07-20  8:05       ` Nick Piggin
2009-07-20  8:05       ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-20  9:59       ` Benjamin Herrenschmidt [this message]
2009-07-20  9:59         ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Benjamin Herrenschmidt
2009-07-20  9:59         ` Benjamin Herrenschmidt
2009-07-20 10:39         ` Nick Piggin
2009-07-20 10:39           ` Nick Piggin
2009-07-20 10:39           ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Nick Piggin
2009-07-22 16:31     ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Linus Torvalds
2009-07-22 16:31       ` Linus Torvalds
2009-07-22 16:31       ` Linus Torvalds
2009-07-23  0:53       ` Benjamin Herrenschmidt
2009-07-23  0:53         ` Benjamin Herrenschmidt
2009-07-23  0:53         ` Benjamin Herrenschmidt
2009-07-23  0:59         ` Kumar Gala
2009-07-23  0:59           ` Kumar Gala
2009-07-23  0:59           ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Kumar Gala
2009-07-27 19:11         ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Linus Torvalds
2009-07-27 19:11           ` Linus Torvalds
2009-07-27 19:11           ` Linus Torvalds
2009-07-27 21:35           ` Benjamin Herrenschmidt
2009-07-27 21:35             ` Benjamin Herrenschmidt
2009-07-27 21:35             ` Benjamin Herrenschmidt
2009-07-28  0:17           ` Benjamin Herrenschmidt
2009-07-28  0:17             ` Benjamin Herrenschmidt
2009-07-28  0:17             ` Benjamin Herrenschmidt
2009-07-28  0:17             ` Benjamin Herrenschmidt
2009-07-28  0:17             ` Benjamin Herrenschmidt
2009-07-28  0:25             ` Paul Mundt
2009-07-28  0:25               ` Paul Mundt
2009-07-28  0:25               ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() Paul Mundt
2009-07-28  0:41               ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() Linus Torvalds
2009-07-28  0:41                 ` Linus Torvalds
2009-07-28  0:41                 ` Linus Torvalds
2009-07-16  1:36 ` Michael Ellerman
2009-07-16  1:36   ` Michael Ellerman
2009-07-16  1:56   ` Benjamin Herrenschmidt
2009-07-16  1:56     ` Benjamin Herrenschmidt
2009-07-16  1:56     ` Benjamin Herrenschmidt
2009-07-20 12:46 ` David Howells
2009-07-20 12:46   ` [RFC/PATCH] mm: Pass virtual address to [__]p{te, ud, md}_free_tlb() David Howells
2009-07-20 12:46   ` [RFC/PATCH] mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() 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=1248083961.30899.5.camel@pasglop \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.