From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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 15:44:57 -0400 [thread overview]
Message-ID: <20080424194457.GA22805@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804242136420.21224@anakin>
On Thu, Apr 24, 2008 at 09:40:15PM +0200, Geert Uytterhoeven wrote:
> 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
Eric already submitted a patch on the xfs list, that should make it to
the tree ASAP.
next prev parent reply other threads:[~2008-04-24 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 7:36 linux-next: Tree for April 24 Stephen Rothwell
2008-04-24 7:45 ` Geert Uytterhoeven
2008-04-24 9:30 ` Stephen Rothwell
2008-04-24 11:12 ` Geert Uytterhoeven
2008-04-25 7:20 ` Stephen Rothwell
2008-04-25 13:32 ` Michael Ellerman
2008-04-25 14:18 ` Sebastian Siewior
2008-04-24 19:40 ` Geert Uytterhoeven
2008-04-24 19:44 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-24 5:04 Stephen Rothwell
2009-04-26 13:20 ` Benny Halevy
2009-04-27 4:21 ` Stephen Rothwell
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=20080424194457.GA22805@infradead.org \
--to=hch@infradead.org \
--cc=geert@linux-m68k.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