From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexander van Heukelum <heukelum@mailshack.com>,
Alexander van Heukelum <heukelum@fastmail.fm>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix find_next_bit breakage on ppc and powerpc
Date: Thu, 17 Apr 2008 08:55:12 +1000 [thread overview]
Message-ID: <18438.33744.389334.543623@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080416144051.GH24383@elte.hu>
Ingo Molnar writes:
>
> * Alexander van Heukelum <heukelum@mailshack.com> wrote:
>
> > Powerpc (and ppc) have their have some code in their bitops.h which
> > used to be exacly the same as asm-generic/bitops/find.h. Include this
> > header instead.
> >
> > This should also fix the compile problems due to the generic
> > find_next_bit changes. Those were fixed by Thomas Gleixner in
> > asm-generic/bitops/find.h earlier.
> >
> > Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm>
>
> thanks, applied. I dropped:
Why are powerpc (and ppc) patches
- not being sent to the powerpc maintainer (me)
- not being cc'd to the linuxppc-dev@ozlabs.org list
- ending up going through the x86 tree?
How come patches to unify x86_32 and x86_64 bitops need to end up
touching powerpc?
Paul.
next prev parent reply other threads:[~2008-04-16 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 16:48 x86: ppc fixes for find_first_bit Alexander van Heukelum
2008-04-16 12:57 ` Ingo Molnar
2008-04-16 13:55 ` [PATCH] x86: fix find_next_bit breakage on ppc and powerpc Alexander van Heukelum
2008-04-16 14:40 ` Ingo Molnar
2008-04-16 15:03 ` Alexander van Heukelum
2008-04-16 22:55 ` Paul Mackerras [this message]
2008-04-17 9:04 ` Alexander van Heukelum
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=18438.33744.389334.543623@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=heukelum@fastmail.fm \
--cc=heukelum@mailshack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®