[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<AM6PR04MB59419D30E1A5A6E2B8CB2F5D88DC2@AM6PR04MB5941.eurprd04.prod.outlook.com>
Date: Tue, 2 Jul 2024 00:04:17 +0000
From: Peng Fan <peng.fan@....com>
To: Cristian Marussi <cristian.marussi@....com>, "Peng Fan (OSS)"
<peng.fan@....nxp.com>
CC: "sudeep.holla@....com" <sudeep.holla@....com>,
"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>
Subject: RE: [PATCH] firmware: arm_scmi: introduce setup_shmem_iomap
> Subject: Re: [PATCH] firmware: arm_scmi: introduce
> setup_shmem_iomap
>
> On Mon, Jul 01, 2024 at 11:01:43AM +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@....com>
> >
> > To get the address of shmem could be generalized by introducing
> > setup_shmem_iomap. Then the duplicated code in mailbox.c and
> optee.c
> > could be dropped.
> >
>
> Hi Peng,
>
> thanks for doing this cleanup, it is certainly needed.
>
> Since I am in the middle of a rework/reshape of the whole SCMI stack
> at the transport layer, I will pick up this patch of yours and integrate in
> my transports-rework related series in order to avoid clashes with all of
> my refactoring
No problem, it is good that you include it in your patchset.
Thanks,
Peng.
... O_o (hopefully later this week I will post
> something...)
>
> Thanks,
> Cristian
Powered by blists - more mailing lists