From: tytso@mit.edu
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: Re: linux-next: ext4 tree build failure
Date: Wed, 9 Dec 2009 21:10:40 -0500 [thread overview]
Message-ID: <20091210021040.GB4735@thunk.org> (raw)
In-Reply-To: <20091210113812.9d1e4bb4.sfr@canb.auug.org.au>
On Thu, Dec 10, 2009 at 11:38:12AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> ERROR: "jbd2_log_start_commit" [fs/ext4/ext4.ko] undefined!
>
> Caused by commit b436b9bef84de6893e86346d8fbf7104bc520645 ("ext4: Wait
> for proper transaction commit on fsync") which I have reverted for today.
Thanks for pointing this out. I've fixed this for tomorrow's build.
- Ted
next prev parent reply other threads:[~2009-12-10 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 0:38 linux-next: ext4 tree build failure Stephen Rothwell
2009-12-10 2:10 ` tytso [this message]
2009-12-10 2:33 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-06-16 4:44 Stephen Rothwell
2009-06-16 20:30 ` Theodore Tso
2009-06-16 22:11 ` Theodore Tso
2009-06-17 5:46 ` Stephen Rothwell
2009-06-17 4:16 ` Pekka Enberg
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=20091210021040.GB4735@thunk.org \
--to=tytso@mit.edu \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox