From: Linus Torvalds <torvalds@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Miller <davem@davemloft.net>,
yinghai@kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, linux-arch@vger.kernel.org
Subject: Re: LMB bits
Date: Tue, 13 Jul 2010 08:11:57 -0700 [thread overview]
Message-ID: <AANLkTikkqL9ppLDaLP6ISkuAawgGF-4ly28sAhdLW3AM@mail.gmail.com> (raw)
In-Reply-To: <1279005164.28659.407.camel@pasglop>
On Tue, Jul 13, 2010 at 12:12 AM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
>
> Ingo, Linus, how to you want to proceed ? We could get the rename patch
> in now, that would make things easier for the ARM folks who have started
> using LMB as well and are currently clashing in linux-next, and keep the
> rest of the rework for the merge window ? Or keep the whole thing for
> the merge window ?
If it's just a rename, and the accidental lmb renames have been all
sorted out, then I'm ok with taking a pure rename that changes nothing
else now, just to make things easier to merge later.
Linus
next prev parent reply other threads:[~2010-07-13 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278031351-23223-1-git-send-email-yinghai@kernel.org>
2010-07-09 7:11 ` LMB bits Benjamin Herrenschmidt
2010-07-09 7:24 ` Ingo Molnar
2010-07-09 7:28 ` David Miller
2010-07-09 7:33 ` Ingo Molnar
2010-07-09 8:24 ` Geert Uytterhoeven
2010-07-09 13:51 ` Ingo Molnar
2010-07-10 0:20 ` David Miller
2010-07-10 3:55 ` David Miller
2010-07-10 11:01 ` Benjamin Herrenschmidt
2010-07-10 20:14 ` David Miller
2010-07-10 20:53 ` Yinghai Lu
2010-07-12 3:24 ` Benjamin Herrenschmidt
2010-07-12 7:38 ` Benjamin Herrenschmidt
2010-07-12 22:34 ` David Miller
2010-07-13 7:12 ` Benjamin Herrenschmidt
2010-07-13 8:54 ` Ingo Molnar
2010-07-13 15:11 ` Linus Torvalds [this message]
2010-07-13 16:45 ` David Miller
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=AANLkTikkqL9ppLDaLP6ISkuAawgGF-4ly28sAhdLW3AM@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).