From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jan Kara <jack@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the ext3 tree
Date: Fri, 8 Aug 2014 11:22:56 +0200 [thread overview]
Message-ID: <20140808092256.GB2398@quack.suse.cz> (raw)
In-Reply-To: <20140808115226.3f4fbeb7@canb.auug.org.au>
On Fri 08-08-14 11:52:26, Stephen Rothwell wrote:
> Hi Jan,
>
> After merging the ext3 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "new_inode_pseudo" [fs/reiserfs/reiserfs.ko] undefined!
>
> Caused by commit 523096294315 ("reiserfs: Avoid warning from unlock_new_inode()").
>
> I have used the ext3 tree from next-20140807 for today.
Ah, sorry. Somehow I've pushed out old version of that commit. I'll fix
that up.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-08-08 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 1:52 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2014-08-08 9:22 ` Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 0:07 Stephen Rothwell
2024-03-07 6:18 ` Winston Wen
2024-03-07 12:03 ` Jan Kara
2023-08-16 0:37 Stephen Rothwell
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2019-01-31 4:14 Stephen Rothwell
2019-01-31 10:11 ` Jan Kara
2019-01-31 22:09 ` Stephen Rothwell
2011-12-28 0:22 Stephen Rothwell
2012-01-02 22:40 ` Jan Kara
2010-03-02 0:36 Stephen Rothwell
2010-03-02 9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03 0:42 ` 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=20140808092256.GB2398@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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.