From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Christoph Hellwig <hch@lst.de>
Cc: jlbec@evilplan.org, akpm@linux-foundation.org,
pantelis.antoniou@konsulko.com, k.opasiak@samsung.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: a configfs update for 4.5, and the configfs tree question
Date: Wed, 06 Jan 2016 09:31:44 -0800 [thread overview]
Message-ID: <1452101504.26125.9.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <1450968671-13699-1-git-send-email-hch@lst.de>
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.
prev parent reply other threads:[~2016-01-06 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 14:51 Christoph Hellwig
2015-12-24 14:51 ` [PATCH] configfs: implement binary attributes Christoph Hellwig
2015-12-29 23:00 ` Joel Becker
2015-12-29 23:26 ` Krzysztof Opasiak
2015-12-30 8:51 ` Pantelis Antoniou
2015-12-29 23:37 ` Krzysztof Opasiak
2015-12-29 23:05 ` a configfs update for 4.5, and the configfs tree question Joel Becker
2016-01-04 11:51 ` Christoph Hellwig
2016-01-04 12:37 ` Fengguang Wu
2016-01-04 20:46 ` Stephen Rothwell
2016-01-05 4:04 ` Joel Becker
2016-01-06 17:31 ` Nicholas A. Bellinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452101504.26125.9.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=k.opasiak@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®