linux-ext4 - Re: [PATCH 0/2] Fix aio completion vs unwritten extents

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 for Android: free password hash cracker in your pocket

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

Message-Id: <D4FBB738-1BAF-4100-BA6E-6CAC184BC30B@mit.edu>
Date:	Fri, 16 Jul 2010 02:30:07 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	linux-fsdevel@...r.kernel.org, xfs@....sgi.com,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix aio completion vs unwritten extents

On Jul 16, 2010, at 2:04 AM, Christoph Hellwig wrote:

> Given that this still hasn't been picked up in any other tree would
> people mind if we push patches 1 and 2 through the XFS tree?
> 
> I some more changes that sit ontop of this, and it would make my
> life a lot easier.

Thanks for bringing this up.  I was going to ask if you had any changes
in patch1 of this series since I was about to put them into the ext4 tree
and I didn't want to have any merge conflicts (or have to force a tree
rewind/rebase) if it turned out if there had been some changes and
some other tree landed in Linus's tree first.

In other words, since we both have patches that depend on your
first patch, one easy way of handling things is that we both put them
into our respective fs trees, and as long as the patch doesn't change
git should do the right thing when Steve or Linus merges them into their
linux-next or linus trees, respectively.

Do you have any objections with this?

									- Ted

--
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