From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexander van Heukelum <heukelum@fastmail.fm>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: linux-next: x86-latest/powerpc-next merge conflict
Date: Mon, 21 Apr 2008 22:10:51 +1000 [thread overview]
Message-ID: <18444.33867.747492.180348@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080421095102.GB1666@elte.hu>
Ingo Molnar writes:
> Paul, do you agree with those generic bitops changes? Just in case it's
Well, it looks OK, but I'm sure people are going to get confused with
fls vs. fls64 vs. __fls all being subtly different. I'd say it's
worth putting a little file in the Documentation directory to explain
it all.
> not obvious from previous discussions: we'll push them upstream via a
> separate pull request, not via usual x86.git changes. They originated
> from x86.git but grew into a more generic improvement for all. They sit
> in x86.git for tester convenience but are of course not pure x86 changes
> anymore.
I'm not sure why the "add __fls to all 64-bit architectures" change
has to be done as a single patch rather than a patch per architecture
going through the architecture maintainers. I suppose that avoids any
problem with some maintainers not sending it upstream quickly. I
would expect that if it is a single cross-architecture patch that it
would go through Andrew Morton, though. But if Andrew wants you to
handle it then I'm happy to give you an Acked-by for it.
Regards,
Paul.
prev parent reply other threads:[~2008-04-21 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 9:12 linux-next: x86-latest/powerpc-next merge conflict Stephen Rothwell
2008-04-21 9:51 ` Ingo Molnar
2008-04-21 11:19 ` Alexander van Heukelum
2008-04-21 11:30 ` Alexander van Heukelum
2008-04-21 12:13 ` Paul Mackerras
2008-04-21 13:07 ` Alexander van Heukelum
2008-04-21 13:36 ` Gabriel Paubert
2008-04-21 14:19 ` Alexander van Heukelum
2008-04-21 12:10 ` Paul Mackerras [this message]
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=18444.33867.747492.180348@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=heukelum@fastmail.fm \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
/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).