From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>
Cc: "Marek Vasut" <marex@denx.de>, "Shawn Guo" <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
stable@vger.kernel.org,
"Francesco Dolcini" <francesco@dolcini.it>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v1] Revert "ARM: dts: imx7: Fix NAND controller size-cells"
Date: Fri, 09 Dec 2022 16:25:28 +0100 [thread overview]
Message-ID: <dbdb4417-a1cf-4613-8f7a-98b524bfdedc@app.fastmail.com> (raw)
In-Reply-To: <bb4e185a-c4db-428b-a1ee-ee1ba767fffb@leemhuis.info>
On Fri, Dec 9, 2022, at 14:30, Thorsten Leemhuis wrote:
> On 08.12.22 17:40, Francesco Dolcini wrote:
>> + Arnd
>
> Arnd, have you seen this? We haven't heard anything from Shawn afaics,
> who normally would take care of a patch like this. Hence could you
> consider picking up the patch at the start of this thread (e.g.
> https://lore.kernel.org/all/20221205152327.26881-1-francesco@dolcini.it/
> ) and send it to Linus in the next 48 hours? It seems low-risk and fixes
> a regression introduced this cycle various people care about. That's why
> I'll likely ask Linus to consider picking this up directly before
> releasing 6.1, if I don't hear anything from you soon. But I'd prefer if
> the patch would go through at least somewhat the proper channels;
> alternatively a ACK from you to signal Linus "yeah, pick this up" would
> help as well.
Done now.
Arnd
next prev parent reply other threads:[~2022-12-09 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:23 [PATCH v1] Revert "ARM: dts: imx7: Fix NAND controller size-cells" Francesco Dolcini
2022-12-05 16:26 ` Marek Vasut
2022-12-05 17:58 ` Miquel Raynal
2022-12-05 18:07 ` Marek Vasut
2022-12-05 18:15 ` Francesco Dolcini
2022-12-05 18:18 ` Miquel Raynal
2022-12-05 18:52 ` Marek Vasut
2022-12-05 19:07 ` Francesco Dolcini
2022-12-06 10:16 ` Miquel Raynal
2022-12-06 19:02 ` Marek Vasut
2022-12-07 7:49 ` Francesco Dolcini
2022-12-08 10:51 ` Miquel Raynal
2022-12-08 11:13 ` Thorsten Leemhuis
2022-12-08 13:21 ` Marek Vasut
2022-12-08 13:49 ` Francesco Dolcini
2022-12-08 13:54 ` Marek Vasut
2022-12-08 16:26 ` Francesco Dolcini
2022-12-08 16:40 ` Francesco Dolcini
2022-12-09 13:30 ` Thorsten Leemhuis
2022-12-09 15:25 ` Arnd Bergmann [this message]
2022-12-09 15:38 ` Miquel Raynal
2022-12-05 16:31 ` Miquel Raynal
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=dbdb4417-a1cf-4613-8f7a-98b524bfdedc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=regressions@leemhuis.info \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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).