From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Adrian Bunk <bunk@kernel.org>,
sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
zippel@linux-m68k.org, linux-ext4@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: ext4 compile error on m68k
Date: Thu, 10 Apr 2008 16:11:32 +0530 [thread overview]
Message-ID: <20080410104059.GA23116@skywalker> (raw)
In-Reply-To: <Pine.LNX.4.64.0804051345180.7216@anakin>
On Sat, Apr 05, 2008 at 01:48:02PM +0200, Geert Uytterhoeven wrote:
> On Sat, 5 Apr 2008, Adrian Bunk wrote:
> > Commit aa02ad67d9b308290fde390682cd039b29f7ab85
> > "ext4: Add ext4_find_next_bit()" causes the following regression:
> >
> > <-- snip -->
> >
> > ...
> > CC [M] fs/ext4/mballoc.o
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/ext4/mballoc.c: In function 'mb_find_next_bit':
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/ext4/mballoc.c:696: error: implicit declaration of function 'generic_find_next_le_bit'
> > make[3]: *** [fs/ext4/mballoc.o] Error 1
> >
> > <-- snip -->
>
> Known issue. The ext4 developers added a #define (with a different name than in
> the patch comment) in the commit below, but forgot to make sure
> generic_find_next_le_bit() is actually available.
>
generic_find_next_le_bit is defined in lib/find_next_bit.c.
But m68k doesn't want to use the GENERIC_FIND_NEXT_BIT. Can I request
somebody knowledgeable about m68k to give a try in implementing
generic_find_next_le_bit equivalent on m68k ?
-aneesh
next prev parent reply other threads:[~2008-04-10 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 10:24 ext4 compile error on m68k Adrian Bunk
2008-04-05 10:24 ` Adrian Bunk
2008-04-05 11:48 ` Geert Uytterhoeven
2008-04-10 10:41 ` Aneesh Kumar K.V [this message]
2008-04-10 11:26 ` Aneesh Kumar K.V
2008-04-10 11:48 ` Andreas Schwab
2008-04-10 13:58 ` Aneesh Kumar K.V
2008-04-10 14:01 ` Christoph Hellwig
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=20080410104059.GA23116@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sct@redhat.com \
--cc=zippel@linux-m68k.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.