From: Andrew Morton <akpm@linux-foundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
Christoph Hellwig <hch@lst.de>,
Daniel Baluta <daniel.baluta@intel.com>,
jlbec@evilplan.org, linux-iio@vger.kernel.org,
linux-fsdevel@vger.kernel.org, lars@metafoo.de, knaack.h@gmx.de,
linux-kernel@vger.kernel.org, octavian.purdila@intel.com,
pebolle@tiscali.nl, patrick.porlan@intel.com,
adriana.reus@intel.com, constantin.musca@intel.com,
marten@intuitiveaerial.com, cristina.opriceana@gmail.com,
pmeerw@pmeerw.net, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v10 1/5] configfs: Allow dynamic group creation
Date: Tue, 17 Nov 2015 15:47:16 -0800 [thread overview]
Message-ID: <20151117154716.48f5a2955b2ce4422dcbc763@linux-foundation.org> (raw)
In-Reply-To: <564860CC.7000206@kernel.org>
On Sun, 15 Nov 2015 10:39:08 +0000 Jonathan Cameron <jic23@kernel.org> wrote:
> On 11/11/15 06:43, Jonathan Cameron wrote:
> >
> >
> > On 10 November 2015 21:12:37 GMT+00:00, Andrew Morton <akpm@linux-foundation.org> wrote:
> >> On Tue, 10 Nov 2015 07:51:26 +0100 Christoph Hellwig <hch@lst.de>
> >> wrote:
> >>
> >>> is this simple addition something you could still send on to Linus
> >>> for this merge window? I would make my life easier to have it in
> >>> so I could start using it in patches for various trees in the next
> >>> merge window.
> >>
> >> It's super late, but the configfs changes are obviously safe to
> >> existing code.
> >>
> >> What about the IIO changes? Will someone be merging them for 4.5-rc1,
> >> or something else?
> > Yes. I'll take the IIO bits and ultimately they'll go through Greg KH for the 4.5
> > merge window.
> >
> Hi Andrew,
>
> Just taken a quick look at your mmotm list and see this ended up in the
> mainline later group (fair enough given the timing!).
> As such shall we fall back to plan b) a special git branch pulled into the trees
> of anyone who cares?
>
> I'll base such a tree on some obvious point in Linus' tree (either 4.4 or 4.5-rc1)
> That way I can get the IIO stuff queued up asap and we can build on that going
> forward during this cycle.
I plan to send configfs-allow-dynamic-group-creation.patch to Linus
this week. I'll retain
iio-core-introduce-iio-configfs-support.patch
iio-core-introduce-iio-software-triggers.patch
iio-core-introduce-iio-software-triggers-fix.patch
iio-trigger-introduce-iio-hrtimer-based-trigger.patch
iio-documentation-add-iio-configfs-documentation.patch
with a view to dropping them once I see them turn up in linux-next.
next prev parent reply other threads:[~2015-11-17 23:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 15:33 [PATCH v10 0/5] Add initial configfs support for IIO Daniel Baluta
2015-10-23 15:33 ` [PATCH v10 1/5] configfs: Allow dynamic group creation Daniel Baluta
2015-11-06 7:50 ` Christoph Hellwig
2015-11-06 8:48 ` Daniel Baluta
2015-11-06 9:31 ` Lars-Peter Clausen
[not found] ` <A334FE9C-F187-4304-AA98-6A40347AF731@jic23.retrosnub.co.uk>
2015-11-07 13:09 ` Christoph Hellwig
2015-11-08 15:30 ` Jonathan Cameron
2015-11-10 6:51 ` Christoph Hellwig
2015-11-10 21:12 ` Andrew Morton
2015-11-11 6:43 ` Jonathan Cameron
2015-11-15 10:39 ` Jonathan Cameron
2015-11-17 23:47 ` Andrew Morton [this message]
2015-11-18 7:33 ` Jonathan Cameron
2015-11-29 17:27 ` Jonathan Cameron
2015-12-02 18:32 ` Jonathan Cameron
2015-11-11 23:08 ` Joel Becker
2015-10-23 15:33 ` [PATCH v10 2/5] iio: core: Introduce IIO configfs support Daniel Baluta
2015-10-24 9:11 ` Matt Ranostay
2015-10-23 15:33 ` [PATCH v10 3/5] iio: core: Introduce IIO software triggers Daniel Baluta
2015-10-23 16:38 ` [PATCH] iio: core: fix ptr_ret.cocci warnings kbuild test robot
2015-10-23 16:38 ` [PATCH v10 3/5] iio: core: Introduce IIO software triggers kbuild test robot
2015-10-23 15:33 ` [PATCH v10 4/5] iio: trigger: Introduce IIO hrtimer based trigger Daniel Baluta
2015-10-23 15:33 ` [PATCH v10 5/5] iio: Documentation: Add IIO configfs documentation Daniel Baluta
2015-10-27 8:35 ` Crt Mori
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=20151117154716.48f5a2955b2ce4422dcbc763@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adriana.reus@intel.com \
--cc=constantin.musca@intel.com \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=hch@lst.de \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=jic23@kernel.org \
--cc=jlbec@evilplan.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marten@intuitiveaerial.com \
--cc=octavian.purdila@intel.com \
--cc=patrick.porlan@intel.com \
--cc=pebolle@tiscali.nl \
--cc=pmeerw@pmeerw.net \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).