From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: max.krummenacher@gmx.de,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Max Krummenacher <max.krummenacher@toradex.com>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH] Revert "ARM: dts: imx: move nand related property under nand@0"
Date: Fri, 6 Mar 2026 08:12:48 +0100 [thread overview]
Message-ID: <502e876d-3627-4d9b-a02b-d2a708ae67e8@kernel.org> (raw)
In-Reply-To: <aaoI7TqtClwSKTLg@lizhi-Precision-Tower-5810>
On 05/03/2026 23:51, Frank Li wrote:
> On Thu, Mar 05, 2026 at 09:37:26PM +0100, Krzysztof Kozlowski wrote:
>> On 05/03/2026 21:05, Frank Li wrote:
>>> On Mon, Mar 02, 2026 at 10:49:28AM -0500, Frank Li wrote:
>>>> On Mon, Mar 02, 2026 at 11:53:00AM +0100, Max Krummenacher wrote:
>>>>> for our NAND-based modules, and our CI no longer produces any useful
>>>>> results as a consequence.
>>>>>
>>>>> I strongly believe that, as an immediate first step, the commit
>>>>> that moved the DT NAND chip configuration into its subnode should
>>>>> be reverted.
>>>>
>>>> As my previous said, can do partial revert? Just add back property under
>>>> gpmi and keep nand@0 node.
>>>>
>>>> For example
>>>>
>>>> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-skov-cpu.dtsi
>>>> +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-skov-cpu.dtsi
>>>> @@ -260,14 +260,10 @@ fixed-link {
>>>> &gpmi {
>>>> pinctrl-names = "default";
>>>> pinctrl-0 = <&pinctrl_gpmi_nand>;
>>>> + nand-on-flash-bbt;
>>>> #address-cells = <1>;
>>>> #size-cells = <0>;
>>>> status = "okay";
>>>>
>>>> Remove "- nand@0" part. You can use "git add -p" to do that.
>>>
>>> Do you plan rework this patch as what I said?
>>
>> Issue and revert were posted two weeks ago. That's maximum time to
>> handle regression.
>
> Any docuement said these maxium times, I also want to know other maximum
Just read the regression and bug handling docs in the kernel.
> time, such as
> what's max time maintainer need reply? Many patch is not any
> reponse for long time.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-06 7:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 15:11 [PATCH] Revert "ARM: dts: imx: move nand related property under nand@0" max.oss.09
2026-02-19 16:01 ` Frank Li
2026-02-19 16:30 ` Francesco Dolcini
2026-02-19 17:06 ` Max Krummenacher
2026-02-19 19:41 ` Frank Li
2026-02-25 17:40 ` Max Krummenacher
2026-02-25 17:51 ` Frank Li
2026-02-26 12:47 ` Max Krummenacher
2026-02-26 15:12 ` Frank Li
2026-03-02 10:53 ` Max Krummenacher
2026-03-02 15:49 ` Frank Li
2026-03-05 20:05 ` Frank Li
2026-03-05 20:37 ` Krzysztof Kozlowski
2026-03-05 22:51 ` Frank Li
2026-03-06 7:12 ` Krzysztof Kozlowski [this message]
2026-03-09 10:41 ` Max Krummenacher
2026-03-09 14:49 ` Frank Li
2026-03-06 15:24 ` 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=502e876d-3627-4d9b-a02b-d2a708ae67e8@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.krummenacher@gmx.de \
--cc=max.krummenacher@toradex.com \
--cc=peng.fan@nxp.com \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--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