LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andreas Dilger <adilger@sun.com>,
sct@redhat.com, akpm@linux-foundation.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] fs/jbd/journal.c: cleanups
Date: Mon, 18 Feb 2008 08:28:58 -0500 [thread overview]
Message-ID: <20080218132858.GA12568@mit.edu> (raw)
In-Reply-To: <20080218131209.GB21080@cs181133002.pp.htv.fi>
On Mon, Feb 18, 2008 at 03:12:09PM +0200, Adrian Bunk wrote:
> If me resending this old patch collides with something finally getting a
> user this part of my patch shouldn't be applied now (but you might get
> it again in 6 months if it's still unused...).
>
> But generally such conflicts would become visible if "known development
> trees that are intended for mainline" were in -mm.
It *has* been in -mm, except for periods when akpm has dropped it due
to conflicts due to the "must have an in-tree user" doctrinaire
attitude due to a conflict with the r/o bind patch.
Did you actually try to do a compile test, or only made sure the patch
would apply? The patch won't collide at application time, but it
would when you compile it....
- Ted
next prev parent reply other threads:[~2008-02-18 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 8:19 Adrian Bunk
2008-02-18 7:04 ` Andreas Dilger
2008-02-18 7:12 ` Ingo Molnar
2008-02-18 11:49 ` Theodore Tso
2008-02-18 12:57 ` Ingo Molnar
2008-02-18 13:31 ` Theodore Tso
2008-02-18 13:55 ` Ingo Molnar
2008-02-18 13:12 ` Adrian Bunk
2008-02-18 13:28 ` Theodore Tso [this message]
2008-02-27 19:39 ` Adrian Bunk
2008-02-18 13:31 ` Ingo Molnar
2008-02-18 15:11 ` Theodore Tso
2008-02-18 16:22 ` Ingo Molnar
2008-02-27 21:20 ` [2.6 patch] unexport journal_update_superblock Adrian Bunk
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=20080218132858.GA12568@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
--subject='Re: [2.6 patch] fs/jbd/journal.c: cleanups' \
/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
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).