IIO 3.6 merge window now closed.
Jonathan Cameron
maintainerHi All,
As Linus has pretty much said he won't do another release candidate, the 3.6 merge window will open in approximately 1 week. For IIO I'm copying Greg's policy with staging (for obvious reasons ;) and closing our merge window now. Rather tediously this means cutting a few of my own patches off. Oh well got to be fair about things and I'll have those queued up for 3.7 nice and early!
Obviously fixes can still get queued up for 3.6, but will probably not go upstream until after 3.6-rc1. As ever, please make sure that fixes are entirely separate from improvements / feature enhancements / new drivers.
Jonathan
Dear Jonathan,
There is some bugs I have fixed for Kfifo. I am not sure whether
it is already fixed by anyone else. Where can I see the latest code for Kfifo? The rc5 does not even include your fix about poll. I guess it is not "latest" enough. There are also two directories for IIO. One is under staging and one is not. Clearly none of them works well since it lacks a lot of files/defines.
Thanks.
Best Regards,
Ge GAO
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Cameron
Sent: Monday, July 16, 2012 1:26 AM
To: linux-iio
Subject: IIO 3.6 merge window now closed.
Hi All,
As Linus has pretty much said he won't do another release candidate, the 3.6 merge window will open in approximately
1 week. For IIO I'm copying Greg's policy with staging (for obvious reasons ;) and closing our merge window now.
Rather tediously this means cutting a few of my own patches off. Oh well got to be fair about things and I'll have those queued up for 3.7 nice and early!
Obviously fixes can still get queued up for 3.6, but will probably not go upstream until after 3.6-rc1. As ever, please make sure that fixes are entirely separate from improvements / feature enhancements / new drivers.
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html