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]
Message-ID: <1452101504.26125.9.camel@haakon3.risingtidesystems.com>
Date:	Wed, 06 Jan 2016 09:31:44 -0800
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Christoph Hellwig <hch@....de>
Cc:	jlbec@...lplan.org, akpm@...ux-foundation.org,
	pantelis.antoniou@...sulko.com, k.opasiak@...sung.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: a configfs update for 4.5, and the configfs tree question

On Thu, 2015-12-24 at 15:51 +0100, Christoph Hellwig wrote:
> Hi all,
> 
> I really want the configfs change in this series to go into 4.5.  Originally
> both Pantelis and I had changes ontop that would require it in a stable
> non-rebased branch, but one or both of those might not make the cut.
> 
> As this has been a problem with a increased configfs actitivly lately I'd
> like to volunteer to co-maintain configfs and keep a git tree that can
> be used as stable baseline for all involved parties instead of the
> patch-only -mm tree or occasional merge through the SCSI target tree.
> 
> I've started out with just this patch in my tree:
> 
> git://git.infradead.org/users/hch/vfs.git configfs-for-4.5
> 
> or gitweb:
> 
> http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/configfs-for-4.5
> 
> I know Krzysztof also had pending changes and I'd be happy to collect them
> as well.

Wrt to Krzysztof's set of aforementioned configfs patches, they have
been in target-pending/for-next for the last few weeks now..

Since the larger set of Andrzej's usb-gadget target changes depend upon
these configfs changes, it makes sense to keep them together in the
target tree.

Beyond that, I'm glad to see a dedicated configfs tree.

Thanks HCH.




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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ