On 17 November 2015 23:47:16 GMT+00:00, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >On Sun, 15 Nov 2015 10:39:08 +0000 Jonathan Cameron <jic23@xxxxxxxxxx> >wrote: > >> On 11/11/15 06:43, Jonathan Cameron wrote: >> > >> > >> > On 10 November 2015 21:12:37 GMT+00:00, Andrew Morton ><akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> On Tue, 10 Nov 2015 07:51:26 +0100 Christoph Hellwig <hch@xxxxxx> >> >> 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. That's great. Thanks. Jonathan -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
