[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DB9PR04MB84613EEEC8EA13469757FF8B88B02@DB9PR04MB8461.eurprd04.prod.outlook.com>
Date: Tue, 30 Jul 2024 14:24:17 +0000
From: Peng Fan <peng.fan@....com>
To: Cristian Marussi <cristian.marussi@....com>
CC: "Peng Fan (OSS)" <peng.fan@....nxp.com>, "sudeep.holla@....com"
<sudeep.holla@....com>, "robh@...nel.org" <robh@...nel.org>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>, "conor+dt@...nel.org"
<conor+dt@...nel.org>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "arm-scmi@...r.kernel.org"
<arm-scmi@...r.kernel.org>, "devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>
Subject: RE: [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout value from
device tree
Hi Cristian,
> Subject: Re: [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout
> value from device tree
>
> On Thu, Jul 18, 2024 at 02:24:15AM +0000, Peng Fan wrote:
> > Hi Cristian,
> >
>
> Hi Peng,
>
> > > Subject: [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout
> > > value from device tree
> >
> > The binding has got R-b from Rob, will you pick this patch in your
> > next Patchset?
> >
>
> I am going to post a new transport_drivers_V3 and, as a separate series
> on top of that, your latest "max-rx-timeuout" DT patch as reviewed by
> Rob, plus the related new logic based on transport_drivers_V3 and a
> few more similar changes as requested by Nikunj.
Ok, so your V3 not include this patchset. Do you have time to give
a look on the 2nd patch? We are still waiting this got R-b to land
this in Google GKI kernel.
Thanks,
Peng.
>
> Thanks,
> Cristian
Powered by blists - more mailing lists