From: Michael Walle <michael@walle.cc>
To: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Arnd Bergmann <arnd@arndb.de>, Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH v2 0/7] soc: fsl: guts: cleanups and serial_number support
Date: Mon, 21 Feb 2022 11:41:58 +0100 [thread overview]
Message-ID: <1e46ae6508997c2bb3f1f0c922ae81d8@walle.cc> (raw)
In-Reply-To: <20220209163242.430265-1-michael@walle.cc>
Hi,
any news here? Through which tree is this supposed to go?
Am 2022-02-09 17:32, schrieb Michael Walle:
> This series converts the guts driver from a platform driver to just an
> core_initcall. The driver itself cannot (or rather should never) be
> unloaded because others depends on detecting the current SoC revision
> to apply chip errata. Other SoC drivers do it the same way. Overall I
> got rid of all the global static variables.
>
> The last patch finally adds unique id support to the guts driver. But
> because the binding [1] for the security fuse processor is still
> pending,
> it is marked as RFC.
As I was about to resend this series without the RFC tag, I noticed
that I forgot to mark patch 7/7 as RFC in v2 anyway. So no need for
resending.
The binding was acked by Rob and already picked up via the nvmem tree.
-michael
>
> [1]
> https://lore.kernel.org/linux-devicetree/20220127163728.3650648-2-michael@walle.cc/
>
> changes since v1:
> - call kfree() in error case, thanks Dan
> - add missing of_node_put(np), thanks Dan
>
> Michael Walle (7):
> soc: fsl: guts: machine variable might be unset
> soc: fsl: guts: remove module_exit() and fsl_guts_remove()
> soc: fsl: guts: embed fsl_guts_get_svr() in probe()
> soc: fsl: guts: allocate soc_dev_attr on the heap
> soc: fsl: guts: use of_root instead of own reference
> soc: fsl: guts: drop platform driver
> soc: fsl: guts: add serial_number support
>
> drivers/soc/fsl/guts.c | 219 ++++++++++++++++++++++-------------------
> 1 file changed, 118 insertions(+), 101 deletions(-)
prev parent reply other threads:[~2022-02-21 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:32 [PATCH v2 0/7] soc: fsl: guts: cleanups and serial_number support Michael Walle
2022-02-09 16:32 ` [PATCH v2 1/7] soc: fsl: guts: machine variable might be unset Michael Walle
2022-02-09 16:32 ` [PATCH v2 2/7] soc: fsl: guts: remove module_exit() and fsl_guts_remove() Michael Walle
2022-02-09 16:32 ` [PATCH v2 3/7] soc: fsl: guts: embed fsl_guts_get_svr() in probe() Michael Walle
2022-02-09 16:32 ` [PATCH v2 4/7] soc: fsl: guts: allocate soc_dev_attr on the heap Michael Walle
2022-02-09 16:32 ` [PATCH v2 5/7] soc: fsl: guts: use of_root instead of own reference Michael Walle
2022-02-09 16:32 ` [PATCH v2 6/7] soc: fsl: guts: drop platform driver Michael Walle
2022-02-09 16:32 ` [PATCH v2 7/7] soc: fsl: guts: add serial_number support Michael Walle
2022-02-10 16:20 ` [PATCH v2 0/7] soc: fsl: guts: cleanups and " Arnd Bergmann
2022-02-21 10:41 ` Michael Walle [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=1e46ae6508997c2bb3f1f0c922ae81d8@walle.cc \
--to=michael@walle.cc \
--cc=Sudeep.Holla@arm.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox