Hi Stephen,
Can you add the clk-fixes branch to linux-next's pending-fixes branch?
Krzysztof mentioned that it wasn't in there and some CI uses that. The
clk-fixes branch is always merged into the clk-next branch of clk.git
and usually it is fully merged into Linus' tree before the next release.
I accumulate clk framework and driver fixes on this branch and send code
from here after the merge window closes.
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git#clk-fixes
Hi Stephen,
On Thu, 28 Mar 2024 18:06:43 -0700 Stephen Boyd <[email protected]> wrote:
>
> Can you add the clk-fixes branch to linux-next's pending-fixes branch?
> Krzysztof mentioned that it wasn't in there and some CI uses that. The
> clk-fixes branch is always merged into the clk-next branch of clk.git
> and usually it is fully merged into Linus' tree before the next release.
> I accumulate clk framework and driver fixes on this branch and send code
> from here after the merge window closes.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git#clk-fixes
Added from Tuesday.
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]