linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
	"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout value from device tree
Date: Tue, 30 Jul 2024 15:56:32 +0100	[thread overview]
Message-ID: <Zqj_ILnsWRHmSWaQ@pluto> (raw)
In-Reply-To: <DB9PR04MB84613EEEC8EA13469757FF8B88B02@DB9PR04MB8461.eurprd04.prod.outlook.com>

On Tue, Jul 30, 2024 at 02:24:17PM +0000, Peng Fan wrote:
> 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.
> 

As said above, your max-rx-timeout-ms DT patch (with Rob R-b) and more is 
included in this small series (just posted):

https://lore.kernel.org/linux-arm-kernel/20240730144707.1647025-1-cristian.marussi@arm.com/T/#t

based on top of transport_drivers_V3.

Thanks,
Cristian


  reply	other threads:[~2024-07-30 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 14:09 [PATCH V3 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms Peng Fan (OSS)
2024-07-09 14:09 ` [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout value from device tree Peng Fan (OSS)
2024-07-18  2:24   ` Peng Fan
2024-07-18  6:11     ` Krzysztof Kozlowski
2024-07-18  6:22       ` Peng Fan
2024-07-30 11:31     ` Cristian Marussi
2024-07-30 14:24       ` Peng Fan
2024-07-30 14:56         ` Cristian Marussi [this message]
2024-07-11 21:05 ` [PATCH V3 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms Rob Herring (Arm)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zqj_ILnsWRHmSWaQ@pluto \
    --to=cristian.marussi@arm.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).