From: Heiko Stuebner <heiko@sntech.de>
To: Lee Jones <lee@kernel.org>
Cc: srini@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v4 2/2] mfd: qnap-mcu: Hook up the eeprom sub-device
Date: Fri, 21 Nov 2025 16:49:05 +0100 [thread overview]
Message-ID: <2807481.mvXUDI8C0e@phil> (raw)
In-Reply-To: <20251121120914.GC1117685@google.com>
Hi Lee,
Am Freitag, 21. November 2025, 13:09:14 Mitteleuropäische Normalzeit schrieb Lee Jones:
> On Thu, 20 Nov 2025, Heiko Stuebner wrote:
> > 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.
No worries and thanks for re-adding the patch.
Heiko
next prev parent reply other threads:[~2025-11-21 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 23:29 [PATCH v4 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Heiko Stuebner
2025-11-03 23:29 ` [PATCH v4 1/2] nvmem: Add driver for the eeprom in qnap-mcu controllers Heiko Stuebner
2025-11-03 23:29 ` [PATCH v4 2/2] mfd: qnap-mcu: Hook up the eeprom sub-device Heiko Stuebner
2025-11-13 15:58 ` (subset) " Lee Jones
2025-11-20 19:36 ` Heiko Stuebner
2025-11-21 12:09 ` Lee Jones
2025-11-21 15:49 ` Heiko Stuebner [this message]
2025-11-05 17:02 ` (subset) [PATCH v4 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Srinivas Kandagatla
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=2807481.mvXUDI8C0e@phil \
--to=heiko@sntech.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.