From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH RESEND v2 0/7] soc: fsl: guts: cleanups and serial_number support
Date: Mon, 27 Jun 2022 14:53:21 +0800 [thread overview]
Message-ID: <20220627065321.GA819983@dragon> (raw)
In-Reply-To: <0bde7550b0bbd1b0a478139d296f92a2@walle.cc>
On Wed, Jun 22, 2022 at 01:03:33PM +0200, Michael Walle wrote:
> Am 2022-04-04 11:56, schrieb Michael Walle:
> > [Resend because of new development cycle. Shawn, can this series get
> > through your tree? Sorry you weren't on CC on the former submissions.]
> >
> > 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. DT
> > binding can be found at:
> > Documentation/devicetree/bindings/nvmem/fsl,layerscape-sfp.yaml
> >
> > 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(-)
>
> There goes another kernel release without any comments on this
> series :(
>
> Shawn, can you pick this up and give it some time in linux-next?
Okay, I just picked the series up to IMX tree.
Leo, let me know if you want to drop it from IMX tree.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-27 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:56 [PATCH RESEND v2 0/7] soc: fsl: guts: cleanups and serial_number support Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 1/7] soc: fsl: guts: machine variable might be unset Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 2/7] soc: fsl: guts: remove module_exit() and fsl_guts_remove() Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 3/7] soc: fsl: guts: embed fsl_guts_get_svr() in probe() Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 4/7] soc: fsl: guts: allocate soc_dev_attr on the heap Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 5/7] soc: fsl: guts: use of_root instead of own reference Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 6/7] soc: fsl: guts: drop platform driver Michael Walle
2022-04-04 9:56 ` [PATCH RESEND v2 7/7] soc: fsl: guts: add serial_number support Michael Walle
2022-06-22 11:03 ` [PATCH RESEND v2 0/7] soc: fsl: guts: cleanups and " Michael Walle
2022-06-27 6:53 ` Shawn Guo [this message]
2022-06-28 18:20 ` Leo Li
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=20220627065321.GA819983@dragon \
--to=shawnguo@kernel.org \
--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=michael@walle.cc \
--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;
as well as URLs for NNTP newsgroup(s).