Hello Stephen,
Kishon has asked me to co-maintain the linux-phy subsystem [1], so can
you please switch the linux-phy tree to new location [2] and list both
of us as as contacts for this tree.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit/?h=fixes&id=c31cd5a5b2f2e5c645f90a788ca6961a8dbbb2fb
[2]: git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
Thanks
--
~Vinod
Hi Vinod,
On Tue, 28 Apr 2020 10:48:04 +0530 Vinod Koul <[email protected]> wrote:
>
> Kishon has asked me to co-maintain the linux-phy subsystem [1], so can
> you please switch the linux-phy tree to new location [2] and list both
> of us as as contacts for this tree.
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit/?h=fixes&id=c31cd5a5b2f2e5c645f90a788ca6961a8dbbb2fb
> [2]: git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
Changes done.
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.
--
Cheers,
Stephen Rothwell
[email protected]