Re: [PATCH v8 00/17] power: sequencing: implement the subsystem and add first users

Bjorn Helgaas
2024-06-05T17:56:11Z

On Tue, Jun 04, 2024 at 08:24:34PM +0200, Bartosz Golaszewski wrote:
> On Tue, Jun 4, 2024 at 7:19 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > On Tue, May 28, 2024 at 09:03:08PM +0200, Bartosz Golaszewski wrote:
> > > Note: I am resending this series in its entirety once more for
> > > discussions and reviews. If there won't be any major objections, I'll
> > > then start sending individual bits and pieces to appropriate trees.
> > >
> > > Merging strategy: The DT binding and DTS changes are a no-brainer, they
> > > can go through the wireless, regulator and arm-msm trees separately. The
> > > bluetooth and PCI changes have a build-time dependency on the power
> > > sequencing code. The bluetooth changes also have a run-time dependency on
> > > the PCI pwrctl part. In order to get it into next I plan to pick up the
> > > power sequencing code into my own tree and maintain it. I can then
> > > provide an immutable tag for the BT and PCI trees to pull. I wouldn't
> > > stress about the BT runtime dependency as it will be fixed once all
> > > changes are in next.
> > > ...
> >
> > > ---
> > > base-commit: 6dc544b66971c7f9909ff038b62149105272d26a
> > > change-id: 20240527-pwrseq-76fc025248a2
> >
> > What does this apply to? I don't know what 6dc544b66971 is; it
> > doesn't seem to be in upstream or linux-next.
>
> It's next-20240528 but it also applies to today's next without
> conflicts. What do you want me to base the PCI part when resending?

For PCI, we usually apply things on topic branches based on -rc1, so
that's the easiest.