linux-kernel - Re: (subset) [PATCH v4 2/2] mfd: qnap-mcu: Hook up the eeprom sub-device

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: <20251121120914.GC1117685@google.com>
Date: Fri, 21 Nov 2025 12:09:14 +0000
From: Lee Jones <lee@...nel.org>
To: Heiko Stuebner <heiko@...ech.de>
Cc: srini@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v4 2/2] mfd: qnap-mcu: Hook up the eeprom
 sub-device

On Thu, 20 Nov 2025, Heiko Stuebner wrote:

> Hi Lee,
> 
> Am Donnerstag, 13. November 2025, 16:58:25 Mitteleuropäische Normalzeit schrieb Lee Jones:
> > On Tue, 04 Nov 2025 00:29:42 +0100, Heiko Stuebner wrote:
> > > Add the qnap-mcu-eeprom platform-driver as sub-device for the MCU.
> > > 
> > > 
> > 
> > Applied, thanks!
> > 
> > [2/2] mfd: qnap-mcu: Hook up the eeprom sub-device
> >       commit: 4e2236230b3d6dda4a60111605e25bf482ef7492
> > 
> 
> Somehow I can see the error handling series in your for-mfd-next branch
> but not the patch above.
> 
> Did it get lost somewhere or am I simply too blind?

That's odd.  It was applied, but was then removed.

I cherry-picked it back in.  It should be in -next by tomorrow.

Apologies for the error.

-- 
Lee Jones [李琼斯]