From: "Arnd Bergmann" <arnd@arndb.de>
To: "Frank Li" <Frank.Li@oss.nxp.com>, soc@kernel.org, arm <arm@kernel.org>
Cc: "Frank Li" <Frank.Li@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
dbgh9129@gmail.com, geoffreyhe2@gmail.com, griffin@kroah.com,
lijun01@kylinos.cn, "Pengpeng Hou" <pengpeng@iscas.ac.cn>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: i.MX SoC Changes for v7.3
Date: Thu, 30 Jul 2026 12:28:53 +0200 [thread overview]
Message-ID: <8723f44e-fb43-49ef-b7eb-64267216f53e@app.fastmail.com> (raw)
In-Reply-To: <20260729193402.533533-1-Frank.Li@oss.nxp.com>
On Wed, Jul 29, 2026, at 21:33, Frank.Li@oss.nxp.com wrote:
>
> ----------------------------------------------------------------
> i.MX SoC Changes for v7.3
>
> - Fix OF/device_node reference count leaks in imx_src_init(),
> imx7_src_init(), and the AVIC interrupt controller driver
> - Drop obsolete/unused declarations from `arch/arm/mach-imx/common.h`
> - firmware: imx: scu: Refactor mailbox channel management to use a
> per-instance handle instead of a global one
> - firmware: imx: sm-misc: Add NULL check for `kmalloc` return value in
> syslog_show
> - soc: imx9: Add error handling for `devm_kasprintf` return value
>
Hi Frank,
I pulled this and the other two branches you sent yesterday,
the contents all look good. A few minor points:
- The soc@kernel.org and arm@kernel.org addresses both forward
to soc@lists.linux.dev these days, so just use that one
directly.
- please split the arch/arm/ code changes from the drivers/*
branches, since we have separate branches for upstream as well.
The changes here were fairly small, so I'm not asking you
to resend them for that here.
- It looks like the automated patchwork bot messages again did
not work here. The git://git.kernel.org URLs failed to work
recently and I added a .gitconfig insteadOf rule for it, which
I think makes the pwbot fail to match the URL and not run
its maintenance scripts that update patchwork and send the
email. I've removed the rule again as both now work, but
you might want to send https:// URLs instead of git://
Arnd
next prev parent reply other threads:[~2026-07-30 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 19:33 i.MX SoC Changes for v7.3 Frank.Li
2026-07-30 10:28 ` Arnd Bergmann [this message]
2026-07-30 14:43 ` Frank 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=8723f44e-fb43-49ef-b7eb-64267216f53e@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=arm@kernel.org \
--cc=dbgh9129@gmail.com \
--cc=geoffreyhe2@gmail.com \
--cc=griffin@kroah.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=lijun01@kylinos.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pengpeng@iscas.ac.cn \
--cc=soc@kernel.org \
--cc=u.kleine-koenig@baylibre.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