linux-ext4 - Re: A tree to pull into linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090716115221.GA24875@atrey.karlin.mff.cuni.cz>
Date:	Thu, 16 Jul 2009 13:52:21 +0200
From:	Jan Kara <jack@...e.cz>
To:	Theodore Tso <tytso@....edu>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>, Jan Kara <jack@...e.cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Tweedie <sct@...hat.com>, linux-ext4@...r.kernel.org,
	Andreas Dilger <adilger@....com>
Subject: Re: A tree to pull into linux-next

> On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> > 
> > I am happy to include this, but (no offense) I would like to hear from
> > the ext3 and jbd maintainers (cc'd) about it.
> > 
> 
> The main isssue would be that akpm often has ext3 changes stashed in
> -mm.  Having a separate ext3 tree makes sense, and if Jan wants to
> maintain it, that makes good sense to me, but we should get Andrew's
> sign off, and Jan should make sure he has any ext3/jbd patches that
> might be in -mm, to avoid any potential patch conflicts.
  Yeah. It's upto Andrew. I think he pulls linux-next so he should notice
conflicts. Anyway, I don't mind pushing the changes through him if he
likes it more that way but I've felt that he's rather busy and this
hopefully helps him a bit...

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html