From: Christoph Hellwig <hch@lst.de>
To: Joel Becker <jlbec@evilplan.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Fengguang Wu <fengguang.wu@intel.com>
Cc: akpm@linux-foundation.org, nab@linux-iscsi.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: Mon, 4 Jan 2016 12:51:01 +0100 [thread overview]
Message-ID: <20160104115101.GA26260@lst.de> (raw)
In-Reply-To: <20151229230530.GD32415@noexit.roam.corp.google.com>
On Tue, Dec 29, 2015 at 03:05:30PM -0800, Joel Becker wrote:
>
> Hoi,
>
> I'm well aware that I've caught some reviews and missed some others. I
> support funneling through hch's tree here.
Thanks. I've created a separate repo for configfs:
git://git.infradead.org/users/hch/configfs.git
gitweb:
http://git.infradead.org/users/hch/configfs.git
this has the binary attribute patch with the most important
review fixes, and the patch attached below to add myself as co-maintainer
and update the git repo in MAINTAINERS. I'd like a signoff from you
for that second one and then move it to for-next.
Fengguang, can you give this tree the full buildbot treatment?
Stephen, can you add
git://git.infradead.org/users/hch/configfs.git for-next
to for-next? It's currently emptry but will contain the two commits
from the pending branch as soon as I get the signoff from Joel.
next prev parent reply other threads:[~2016-01-04 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 14:51 a configfs update for 4.5, and the configfs tree question 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 [this message]
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
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=20160104115101.GA26260@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jlbec@evilplan.org \
--cc=k.opasiak@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.