From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: linux-next: Tree for April 24
Date: Thu, 24 Apr 2008 21:40:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804242136420.21224@anakin> (raw)
In-Reply-To: <20080424173626.bcd088e7.sfr@canb.auug.org.au>
On Thu, 24 Apr 2008, Stephen Rothwell wrote:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next. If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
For the second day in a row, m68k builds failed because of
fs/xfs/xfs_fsops.c:527: error: implicit declaration of function 'xfs_icsb_sync_counters_locked'
make[3]: *** [fs/xfs/xfs_fsops.o] Error 1
According to
http://www.linux.sgi.com/archives/xfs/2008-03/msg00202.html, there's a
forward declaration for xfs_icsb_sync_counters_locked() only if HAVE_PERCPU_SB
is defined, i.e. for CONFIG_SMP. This break UP architectures.
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
next parent reply other threads:[~2008-04-24 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080424173626.bcd088e7.sfr@canb.auug.org.au>
2008-04-24 19:40 ` Geert Uytterhoeven [this message]
2008-04-24 19:44 ` linux-next: Tree for April 24 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=Pine.LNX.4.64.0804242136420.21224@anakin \
--to=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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