linux-kernel - Re: linux-next: nfs/ceph tree build failure

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] [day] [month] [year] [list]

Date:	Fri, 8 Jan 2010 16:16:36 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Sage Weil <sage@...dream.net>
Cc:	Trond Myklebust <trond.myklebust@....uio.no>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: linux-next: nfs/ceph tree build failure

Hi Sage,

On Thu, 7 Jan 2010 20:51:45 -0800 (PST) Sage Weil <sage@...dream.net> wrote:
>
> Okay.  I can move it to my tree as well, where I assume it'll need to be 
> when it comes time to merge.

Well, that depends on the order that the two trees get merged into Linus'
tree.  If you get in first, then Trond will have to fix up his tree
before merging (or get Linus to apply my patch as a merge fixup).

One possible thing you could do is to apply both the nfs tree patch and
my patch to your tree (or merge the nfs tree into your tree and apply the
merge fixup), but that will cause a problem if the patch is updated in
the nfs tree (or the nfs tree rebases) ...

So the easiest thing (at leas at this early stage of the development
cycle) is for me to keep applying the merge fixup to my tree when I merge
the later of your two trees into linux-next (this is an automated
process).  Maybe in a few weeks we might do something different.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped