linux-kernel - Re: [PATCH v3 0/2] firmware: arm

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] [day] [month] [year] [list]

Message-ID: <aWTiC78PXRoadeJy@bogus>
Date: Mon, 12 Jan 2026 11:59:07 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Peng Fan <peng.fan@....nxp.com>
Cc: Shawn Guo <shawnguo@...nel.org>, Peng Fan <peng.fan@....com>,
	Cristian Marussi <cristian.marussi@....com>,
	Sudeep Holla <sudeep.holla@....com>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	Pengutronix Kernel Team <kernel@...gutronix.de>,
	Fabio Estevam <festevam@...il.com>, arm-scmi@...r.kernel.org,
	imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] firmware: arm_scmi/imx: Support dump syslog

On Wed, Jan 07, 2026 at 09:34:47AM +0800, Peng Fan wrote:
> On Tue, Jan 06, 2026 at 03:46:29PM +0000, Sudeep Holla wrote:
> >On Mon, Jan 05, 2026 at 08:49:24PM +0800, Peng Fan wrote:
> >> Hi Sudeep,
> >> 
> >> Hope you're doing well. Apologies for following up again, but this v3 patchset
> >> has been pending for quite some time. I wanted to check if everything looks
> >> good on your end.
> >> 
> >
> >Yes overall it looks good to me.
> 
> Thanks a lot.
> 
> >
> ...
> >> Alternatively, I can ask Shawn to pick patch 2 if you only intend to take patch 1.
> >
> >I think that would break build or need to wait for another cycle.
> >I can ack if it can be routed via i.MX tree or need ACK to pick it up myself.
> 
> Shawn,
> 
> Do you plan to pick the two patches with Sudeep's Ack in patch 1? Or
> you prefer to route the patches via SCMI tree with your Ack?

I noticed this morning we are already at -rc5, which is later than my usual PR
timing (I generally aim to send to the SoC team between -rc4 and -rc5). I have
already sent the SCMI PR.

For these changes, would it be acceptable to route them via the i.MX tree if
they are still intended for v7.0/v6.20? If not, I am happy to defer and pick
them up for the merge window after next.

-- 
Regards,
Sudeep