Hi Stephen,
I've noticed your spmi-next [1] branch is not currently tracked by linux-next
[2]. Could you please consider adding it?
There's a machine (MT8195 Tomato Chromebook) that relies on a fix from that
branch to reliably boot, and since the machine is hooked up to KernelCI to run
tests on top of linux-next, having the fix integrated into next would make the
test results more useful, the machine's current upstream support easily
verifiable and regressions detectable.
Thanks,
N?colas
[1] https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git/log/?h=spmi-next
[2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/diff/Next/Trees
Hi Stephen,
On Wed, 06 Dec 2023 15:59:47 -0800 Stephen Boyd <[email protected]> wrote:
>
> Quoting Nícolas F. R. A. Prado (2023-11-29 13:49:21)
> >
> > I've noticed your spmi-next [1] branch is not currently tracked by linux-next
> > [2]. Could you please consider adding it?
>
> I tried[3] but it didn't get added. Maybe it will work this time?
Sorry about that. I am not sure what happened (getting old, I guess
:-)). Thanks for trying again.
I have added it from today.
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]