From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Russell King" <rmk+lkml@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: Yet more ARM breakage in linux-next
Date: Wed, 3 Dec 2008 20:33:57 -0500 [thread overview]
Message-ID: <8bd0f97a0812031733n18184927m2b4fcfa0ed05cd7b@mail.gmail.com> (raw)
In-Reply-To: <200812040952.44957.rusty@rustcorp.com.au>
On Wed, Dec 3, 2008 at 18:22, Rusty Russell wrote:
> On Thursday 04 December 2008 07:11:09 Andrew Morton wrote:
>> On Wed, 3 Dec 2008 19:29:05 +0000
>>
>> Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>> > This seems to be causing lots of ARM breakage:
>> >
>> > lib/find_next_bit.c:183: error: implicit declaration of function '__fls'
>> >
>> > Whoever's responsible,
>>
>> git-blame?
>
> It's me. Turns out sparc, avr32 and arm all don't define __fls in their
> asm/bitops.h, and I'm the first one to use it in generic code.
the Blackfin port also does not ... you going to post a change for
that since the build breaks for Blackfin atm too ?
-mike
next prev parent reply other threads:[~2008-12-04 1:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 19:29 Russell King
2008-12-03 20:41 ` Andrew Morton
2008-12-03 23:22 ` Rusty Russell
2008-12-03 23:37 ` Randy Dunlap
2008-12-03 23:46 ` Andrew Morton
2008-12-04 0:10 ` Alan Cox
2008-12-04 0:01 ` David Miller
2008-12-04 0:18 ` Randy Dunlap
2008-12-04 1:27 ` Rusty Russell
2008-12-04 2:56 ` Stephen Hemminger
2008-12-04 0:31 ` Russell King
2008-12-04 3:06 ` Nicolas Pitre
2008-12-04 1:33 ` Mike Frysinger [this message]
2008-12-04 2:15 ` Rusty Russell
2008-12-04 3:55 ` Mike Frysinger
2008-12-04 9:18 ` Geert Uytterhoeven
2008-12-04 14:12 ` Rusty Russell
2008-12-07 21:50 ` Geert Uytterhoeven
2008-12-08 6:20 ` Rusty Russell
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=8bd0f97a0812031733n18184927m2b4fcfa0ed05cd7b@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®