On Fri, Aug 22, 2025 at 02:23:50PM +0200, Krzysztof Kozlowski wrote:
> On 22/08/2025 13:32, Brian Masney wrote:
> > 7 of the 114 patches in this series needs a v2 with a minor fix. I see
> > several paths forward to merging this. It's ultimately up to Stephen how
> > he wants to proceed.
> >
> > - I send Stephen a PULL request with all of these patches with the minor
> > cleanups to the 7 patches. Depending on the timing, Stephen can merge
> > the other work first, and I deal with cleaning up the merge conflicts.
> > Or he can if he prefers to instead.
> >
> > - Stephen applies everyone else's work first to his tree, and then the
> > good 107 patches in this series. He skips anything that doesn't apply
> > due to other people's work and I follow up with a smaller series.
>
> Both cause cross tree merge conflicts. Anyway, please document clearly
> the dependencies between patches.
This series only touches drivers/clk, so it shouldn't cause any issues
with other subsystems, unless there's a topic branch somewhere, or I'm
missing something?
There are some drivers under drivers/clk/ where there is an entry in the
MAINTAINERS file that's not Stephen, although it wasn't clear to me if
all of those people will send PULL requests to Stephen. I described on
the cover how how the series was broken up.
- Patches 4-70 are for drivers where there is no clk submaintainer
- Patches 71-110 are for drivers where this is an entry in MAINTAINERS
(for drivers/clk)
For the clk subdirectories that had say more than 3 patches, I sent
those off as separate patch series. The ones in this series have an
entry in MAINTAINERS only have a few patches for each maintainer.
As for patch dependencies, patches 111 (clk/divider) and
114 (clk/fixed-factor) should go in last. It doesn't matter the order
everything else goes in.
Brian
