[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gL35QJXECJGnSwPbC3RFWoAD=KGpPdJ0YA1VAPtP1A+Q@mail.gmail.com>
Date: Mon, 28 Nov 2022 14:54:05 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Zhang Rui <rui.zhang@...el.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Guenter Roeck <linux@...ck-us.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
rafael@...nel.org
Subject: Re: linux-next: manual merge of the thermal tree with the pm tree
On Mon, Nov 28, 2022 at 2:48 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> On Mon, Nov 28, 2022 at 02:22:27PM +0100, Daniel Lezcano wrote:
> >
> > Hi,
> >
> > On 28/11/2022 13:51, Rafael J. Wysocki wrote:
> > > Sorry about this, but I cannot fix it myself and Daniel is on an
> > > extended leave.
> > >
> > > Can you just drop it permanently from linux-next and we'll sort this out
> > > when Daniel is back?
> >
> > Yes sorry for that, I'll go back in a couple of days and sort this out
> >
>
> What about the upcoming merge window? At worst Linus has to figure
> out how to solve this complex conflict when pulling either tree...
>
> Linus has already said that there's likely -rc8 of current cycle [1],
> so we have about two weeks to try sorting out the conflict and be ready
> for PR to him.
As I said before, the thermal tree is merged through the PM tree
anyway, so it needs to be addressed in the thermal tree or worked
around somehow. Linus will not see this conflict.
Worst-case I can apply patches directly with an ACK from Daniel.
Thanks!
Powered by blists - more mailing lists