Include Altera's SoCFPGA tree
Hi linux-next maintainers,
Could you please add the SoCFPGA tree to linux-next? The branch contains patches intended for the next merge window for the SoCFPGA subsystem.
Git Repo: https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
Branch: for-next
Thanks,
Dinh Nguyen
Mark Brown
maintainerQuoted 9 lines · Dinh Nguyen
Hi linux-next maintainers,
Could you please add the SoCFPGA tree to linux-next? The branch contains patches intended for the next merge window for the SoCFPGA subsystem.
Git Repo: https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
Branch: for-next
I've added this, all being well it will appear in today's next.
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.
Quoted 27 lines · Mark Brown
Quoted 9 lines · Dinh Nguyen
Hi linux-next maintainers,
Could you please add the SoCFPGA tree to linux-next? The branch contains patches intended for the next merge window for the SoCFPGA subsystem.
Git Repo: https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
Branch: for-next
I've added this, all being well it will appear in today's next.
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.
Quoted 2 lines
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.
Thank you so much!
Dinh