Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	linux-kernel@vger.kernel.org, Alexander Dahl <ada@thorsis.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	linux-mtd@lists.infradead.org, stable@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	"Rob Herring (Arm)" <robh@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] memory: atmel-ebi: Allow deferred probing
Date: Fri, 29 May 2026 09:21:14 +0200	[thread overview]
Message-ID: <54166bd9-7f54-49bf-a12c-b885b1c83207@kernel.org> (raw)
In-Reply-To: <a76e1b63-84cd-49c7-a69f-8b71522dd5e6@leemhuis.info>

On 28/05/2026 16:44, Thorsten Leemhuis wrote:
> On 5/4/26 19:48, Krzysztof Kozlowski wrote:
>>
>> On Wed, 29 Apr 2026 14:59:30 +0200, Alexander Dahl wrote:
>>> After removing of_platform_default_populate() calls the atmel-ebi driver
>>> was affected by deferred probing.  platform_driver_probe() is
>>> incompatible with deferred probing.  This led to atmel-ebi driver
>>> eventually not being probed on at91 sam9x60-curiosity and other sam9x60
>>> based boards.  Subsequently the nand-controller driver (nand-controller
>>> being a child node of ebi) on that platform was not probed and thus raw
>>> NAND flash was inaccessible, preventing devices to boot with rootfs on
>>> raw NAND flash (e.g. with UBI/UBIFS).
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/1] memory: atmel-ebi: Allow deferred probing
>>       https://git.kernel.org/krzk/linux-mem-ctrl/c/754d60ad1c91895be0bc7d771fbf9fb3c9448640
> 
> Lo! What's the status of this regression fix? It seems to be sitting in
> next for a while already. To me as an outsider it looks like this should
> be on track to get it merged for -rc6, as that's when Linus ideally
> wants all regressions fixed; but it looks a bit like this is destined to
> be merged in the next merge window. But I might be entirely wrong here
> -- or I'm right and there are good reasons why the next merge window is
> better here.

Thanks for pinging. This indeed deserves fixing in current RC and I
completely missed that. Or applied on wrong branch and forgot that it is
a fix. I sent RC fix pull request with this now.

Best regards,
Krzysztof

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2026-05-29  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 12:59 [PATCH] memory: atmel-ebi: Allow deferred probing Alexander Dahl
2026-05-04 17:48 ` Krzysztof Kozlowski
2026-05-28 14:44   ` Thorsten Leemhuis
2026-05-29  7:21     ` Krzysztof Kozlowski [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=54166bd9-7f54-49bf-a12c-b885b1c83207@kernel.org \
    --to=krzk@kernel.org \
    --cc=ada@thorsis.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=robh@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