Add IIO trees to linux-next
Hi Stephen,
I would like to request adding the following two branches to linux-next. Both normally merge through Greg's staging tree.
IIO fixes branch which merges through Greg's staging-linus branch.git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git#fixes-togreg
IIO stuff for next merge window which merges through Greg's staging-next branch.git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git#togreg
Both are the same as the staging trees today as Greg accepted a pull request earlier today and I just rebased before sending this.
Thanks,
Jonathan
Hi Jonathan,
Quoted 4 lines · On Wed, 7 Apr 2021 14:05:23 +0100 Jonathan Cameron…
I would like to request adding the following two branches to linux-next. Both normally merge through Greg's staging tree.
Quoted 8 lines
IIO fixes branch which merges through Greg's staging-linus branch.
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git#fixes-togregIIO stuff for next merge window which merges through Greg's staging-next branch.
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git#togregBoth are the same as the staging trees today as Greg accepted a pull request earlier today and I just rebased before sending this.
Added from tomorrow.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected]