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  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]
Date:	Fri, 25 Jul 2014 09:18:34 +1000
From:	Stephen Rothwell <>
To:	Christoph Hellwig <>
Cc:	Al Viro <>,,,
	Andrew Morton <>,
	Linus Torvalds <>,
	Miklos Szeredi <>
Subject: Re: VFS tree for 3.17?

Hi Christoph,

On Thu, 24 Jul 2014 08:30:57 -0700 Christoph Hellwig <> wrote:
> I've pushed out the current queue to:
> git:// vfs-for-3.17
> Stephen, can you include this in linux-next for testing?  I plan to
> send the first two patches to Linus on Saturday as they seems worth
> to fix for this release still, between a user triggered refcount one off
> and a fix for a just introduced warning.

Added from today (called "hch-vfs").

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
     * submitted under GPL v2 (or later) and include the Contributor's
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

Stephen Rothwell

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)

Powered by blists - more mailing lists