From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Hitomi Hasegawa" <hasegawa-hitomi@fujitsu.com>,
"Paul Menzel" <pmenzel@molgen.mpg.de>,
"Brian Norris" <briannorris@chromium.org>,
"Tomer Maimon" <tmaimon77@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Sven Peter" <sven@svenpeter.dev>,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
"Hector Martin" <marcan@marcan.st>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Joel Stanley" <joel@jms.id.au>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH v6] soc: nuvoton: Add SoC info driver for WPCM450
Date: Sat, 11 Feb 2023 02:02:48 +0100 [thread overview]
Message-ID: <Y+bpODkxY3FlCjPg@probook> (raw)
In-Reply-To: <CAMuHMdWo5vHCeE6BeSHrUy12uT7_wFhW-VbQmQ5u+4Q8c7-wYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]
On Fri, Feb 10, 2023 at 11:26:28AM +0100, Geert Uytterhoeven wrote:
> Hi Jonathan,
>
> 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.
> >
> > Usage example:
> >
> > # grep . /sys/devices/soc0/*
> > /sys/devices/soc0/family:Nuvoton NPCM
> > /sys/devices/soc0/revision:A3
> > /sys/devices/soc0/soc_id:WPCM450
> >
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> > Reviewed-by: Joel Stanley <joel@jms.id.au>
> > Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> > ---
> > v6:
> > - Select REGMAP
> > - Rearrange Kconfig structure a bit
>
> Thanks for your patch!
>
> Unfortunately Joel seems to have sent v5 to Arnd instead of v6?
> https://lore.kernel.org/all/20230201051717.1005938-1-joel@jms.id.au
>
> Which is now commit 7dbb4a38bff34493 ("soc:
> nuvoton: Add SoC info driver for WPCM450") in soc/for-next...
>
> > --- /dev/null
> > +++ b/drivers/soc/nuvoton/Kconfig
> > @@ -0,0 +1,17 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +menu "Nuvoton SoC drivers"
> > + depends on ARCH_NPCM || COMPILE_TEST
>
> ... and lacks the above dependency, hence appearing on my radar.
>
> > +
> > +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?
Jonathan
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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 02:02:48 +0100 [thread overview]
Message-ID: <Y+bpODkxY3FlCjPg@probook> (raw)
In-Reply-To: <CAMuHMdWo5vHCeE6BeSHrUy12uT7_wFhW-VbQmQ5u+4Q8c7-wYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]
On Fri, Feb 10, 2023 at 11:26:28AM +0100, Geert Uytterhoeven wrote:
> Hi Jonathan,
>
> 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.
> >
> > Usage example:
> >
> > # grep . /sys/devices/soc0/*
> > /sys/devices/soc0/family:Nuvoton NPCM
> > /sys/devices/soc0/revision:A3
> > /sys/devices/soc0/soc_id:WPCM450
> >
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> > Reviewed-by: Joel Stanley <joel@jms.id.au>
> > Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> > ---
> > v6:
> > - Select REGMAP
> > - Rearrange Kconfig structure a bit
>
> Thanks for your patch!
>
> Unfortunately Joel seems to have sent v5 to Arnd instead of v6?
> https://lore.kernel.org/all/20230201051717.1005938-1-joel@jms.id.au
>
> Which is now commit 7dbb4a38bff34493 ("soc:
> nuvoton: Add SoC info driver for WPCM450") in soc/for-next...
>
> > --- /dev/null
> > +++ b/drivers/soc/nuvoton/Kconfig
> > @@ -0,0 +1,17 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +menu "Nuvoton SoC drivers"
> > + depends on ARCH_NPCM || COMPILE_TEST
>
> ... and lacks the above dependency, hence appearing on my radar.
>
> > +
> > +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?
Jonathan
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-11 1:04 UTC|newest]
Thread overview: 10+ 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
2022-11-03 21:34 ` Jonathan Neuschäfer
2023-02-10 10:26 ` Geert Uytterhoeven
2023-02-10 10:26 ` Geert Uytterhoeven
2023-02-11 1:02 ` Jonathan Neuschäfer [this message]
2023-02-11 1:02 ` Jonathan Neuschäfer
2023-02-11 9:33 ` Geert Uytterhoeven
2023-02-11 9:33 ` Geert Uytterhoeven
2023-02-11 20:13 ` Jonathan Neuschäfer
2023-02-11 20:13 ` Jonathan Neuschäfer
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+bpODkxY3FlCjPg@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 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.