From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jan Kara <jack@suse.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: linux-next: build failure after merge of the ext3 tree
Date: Wed, 3 Mar 2010 11:42:31 +1100 [thread overview]
Message-ID: <20100303114231.c22db82e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100302172757.GE3829@quack.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi Jan,
On Tue, 2 Mar 2010 18:27:57 +0100 Jan Kara <jack@suse.cz> wrote:
>
> I'm sorry. It's my fault. I've modified Christoph's patch but I forgot to
> enable JFS in the test build. Since this isn't the first time something
> like this happened to me, I've changed the way I commit patches. They'll
> first go to for_testing branch and after a build machine runs them through
> allyesconfig and allmodconfig compiles they'll get moved to for_next
> branch. So hopefully stupid mistakes like this one should be avoided for
> future.
Sound like a good plan, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-03 0:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 0:36 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2010-03-02 9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03 0:42 ` Stephen Rothwell [this message]
2011-12-28 0:22 Stephen Rothwell
2012-01-02 22:40 ` Jan Kara
2014-08-08 1:52 Stephen Rothwell
2014-08-08 9:22 ` Jan Kara
2019-01-31 4:14 Stephen Rothwell
2019-01-31 10:11 ` Jan Kara
2019-01-31 22:09 ` Stephen Rothwell
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2023-08-16 0:37 Stephen Rothwell
2024-03-07 0:07 Stephen Rothwell
2024-03-07 6:18 ` Winston Wen
2024-03-07 12:03 ` Jan Kara
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=20100303114231.c22db82e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).