From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
linux-kernel@vger.kernel.org
Cc: "Amarula patchwork" <linux-amarula@amarulasolutions.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Martin Kaiser" <martin@kaiser.cx>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Russell King" <linux@armlinux.org.uk>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] ARM: imx: add missing of_node_put()
Date: Tue, 06 Dec 2022 22:04:31 +0100 [thread overview]
Message-ID: <3e40bfd9-2345-45ea-af1c-b8000b50ac01@app.fastmail.com> (raw)
In-Reply-To: <20221206171049.3316611-1-dario.binacchi@amarulasolutions.com>
On Tue, Dec 6, 2022, at 18:10, Dario Binacchi wrote:
> The 5 patches in the series fix the same problem on different platforms.
> In doing so it is possible to add to each of them the tag "Fixes" which
> identifies the commit they fix.
I think these should be combined into a single patch after all.
It's not a problem to have multiple 'Fixes' tags pointing to
different commits here, as the patches would not get backported
to a different set of kernels.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-12-06 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:10 [PATCH 0/5] ARM: imx: add missing of_node_put() Dario Binacchi
2022-12-06 17:10 ` [PATCH 1/5] ARM: imx25: " Dario Binacchi
2022-12-06 17:10 ` [PATCH 2/5] ARM: imx27: " Dario Binacchi
2022-12-06 17:10 ` [PATCH 3/5] ARM: imx31: " Dario Binacchi
2022-12-06 17:10 ` [PATCH 4/5] ARM: imx35: " Dario Binacchi
2022-12-06 17:10 ` [PATCH 5/5] ARM: imx5: " Dario Binacchi
2022-12-06 21:04 ` Arnd Bergmann [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=3e40bfd9-2345-45ea-af1c-b8000b50ac01@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dario.binacchi@amarulasolutions.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin@kaiser.cx \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).