linux-kernel - Re: [PATCH] firmware: arm_scmi: introduce setup_shmem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZoKxucvEQwNNj6oQ@pluto>
Date: Mon, 1 Jul 2024 14:40:09 +0100
From: Cristian Marussi <cristian.marussi@....com>
To: "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: sudeep.holla@....com, cristian.marussi@....com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	arm-scmi@...r.kernel.org, Peng Fan <peng.fan@....com>
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 ... O_o (hopefully later this week I will post
something...)

Thanks,
Cristian