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

Message-ID: <Pine.LNX.4.64.1001072048420.7474@cobra.newdream.net>
Date:	Thu, 7 Jan 2010 20:51:45 -0800 (PST)
From:	Sage Weil <sage@...dream.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
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

On Fri, 8 Jan 2010, Stephen Rothwell wrote:

> Hi Trond,
> 
> On Thu, 07 Jan 2010 19:18:33 -0500 Trond Myklebust <trond.myklebust@....uio.no> wrote:
> >
> > The patch itself looks correct to me.
> 
> Thanks for the confirmation.

Yep, looks good.

> > How would you like me to proceed? Should I revert the VM changes from
> > the NFS linux-next tree, or would you be OK with keeping the above patch
> > for now?
> 
> I am OK with keeping the patch - we just need to remember it during the
> next merge window.

Okay.  I can move it to my tree as well, where I assume it'll need to be 
when it comes time to merge.

Thanks-
sage
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/