From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
openbmc@lists.ozlabs.org, "Joel Stanley" <joel@jms.id.au>,
"Tomer Maimon" <tmaimon77@gmail.com>,
"Paul Menzel" <pmenzel@molgen.mpg.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Hitomi Hasegawa" <hasegawa-hitomi@fujitsu.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Hector Martin" <marcan@marcan.st>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Brian Norris" <briannorris@chromium.org>,
"Sven Peter" <sven@svenpeter.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] soc: nuvoton: Add SoC info driver for WPCM450
Date: Sat, 11 Feb 2023 21:13:23 +0100 [thread overview]
Message-ID: <Y+f245CgehS4Eet2@probook> (raw)
In-Reply-To: <CAMuHMdVzbSvA=1fm1ArwsN0=vU4-Ke_J7=s=N0i9jc69=Xa0qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Sat, Feb 11, 2023 at 10:33:05AM +0100, Geert Uytterhoeven wrote:
> Hi Jonathan,
>
> On Sat, Feb 11, 2023 at 2:03 AM Jonathan Neuschäfer
> <j.neuschaefer@gmx.net> wrote:
> > On Fri, Feb 10, 2023 at 11:26:28AM +0100, Geert Uytterhoeven wrote:
> > > On Thu, Nov 3, 2022 at 10:37 PM Jonathan Neuschäfer
> > > <j.neuschaefer@gmx.net> wrote:
> > > > Add a SoC information driver for Nuvoton WPCM450 SoCs. It provides
> > > > information such as the SoC revision.
[...]
> > > > +config WPCM450_SOC
> > > > + tristate "Nuvoton WPCM450 SoC driver"
> > > > + default y if ARCH_WPCM450
> > > > + select SOC_BUS
> > > > + select REGMAP
> > > > + help
> > > > + Say Y here to compile the SoC information driver for Nuvoton
> > > > + WPCM450 SoCs.
> > > > +
> > > > + This driver provides information such as the SoC model and
> > > > + revision.
> > > > +
> > > > +endmenu
> > >
> > > Do you plan to send a follow-up patch?
> >
> > Yes, hopefully I'll get around to it a few days after rc1, when the dust
> > of the (upcoming) merge window has settled a bit.
> >
> > Or should I rather send it earlier?
>
> I'd say sooner rather than later.
> If I hadn't found your v6, I would have sent a patch myself to add the
> dependency.
Ok, I'll send it today.
>
> Does the "select REGMAP" fix a build issue? If yes, that's a very good
> reason to send it now...
Unfortunately I wasn't able to find the build issue report.
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-02-11 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 21:34 [PATCH v6] soc: nuvoton: Add SoC info driver for WPCM450 Jonathan Neuschäfer
2023-02-10 10:26 ` Geert Uytterhoeven
2023-02-11 1:02 ` Jonathan Neuschäfer
2023-02-11 9:33 ` Geert Uytterhoeven
2023-02-11 20:13 ` Jonathan Neuschäfer [this message]
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=Y+f245CgehS4Eet2@probook \
--to=j.neuschaefer@gmx.net \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=conor.dooley@microchip.com \
--cc=geert@linux-m68k.org \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=nicolas.ferre@microchip.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robert.jarzmik@free.fr \
--cc=sven@svenpeter.dev \
--cc=tmaimon77@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox