Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-ext4@vger.kernel.org
Subject: Re: ext4 still busted on ext4
Date: Thu, 29 May 2008 16:40:42 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805291638390.2696@anakin> (raw)
In-Reply-To: <20080529140718.GB1180@atrey.karlin.mff.cuni.cz>

On Thu, 29 May 2008, Jan Kara wrote:
> > /usr/src/devel/fs/ext4/mballoc.c: In function 'mb_find_next_bit':
> > /usr/src/devel/fs/ext4/mballoc.c:399: error: implicit declaration of function 'generic_find_next_le_bit'
> > 
> > This has been happening for months.
>   Is there anything wrong with the obvious fix (below)? I don't have a
> way to even compile-test this...

Yes. Including the header only provides the prototype of
generic_find_next_le_bit(), not the actual implementation. So it will
still fail at link time.

There exists a patch to fix it, but I haven't tested it yet. Will do (when
time permits), hopefully before 2.6.26...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

      reply	other threads:[~2008-05-29 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23  6:54 ext4 still busted on ext4 Andrew Morton
2008-05-23  6:55 ` Andrew Morton
2008-05-29 14:07 ` Jan Kara
2008-05-29 14:40   ` Geert Uytterhoeven [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=Pine.LNX.4.64.0805291638390.2696@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.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