From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Claudiu.Beznea@microchip.com, mturquette@baylibre.com,
sboyd@kernel.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] memory: atmel-sdramc: remove the driver
Date: Tue, 3 Jan 2023 14:17:09 +0100 [thread overview]
Message-ID: <414b2785-fba0-1426-d059-befeabe9ddac@linaro.org> (raw)
In-Reply-To: <92347fcb-46b3-d1bf-82f1-960f69300a29@microchip.com>
On 03/01/2023 13:45, Claudiu.Beznea@microchip.com wrote:
>>>> Uh, why does it depend? I understood the changset is bisectable and
>>>> removal of unneeded driver will happen later. Otherwise it is not
>>>> bisectable...
>>>
>>> AT91 devices will fail to boot if this patch is applied and 1/3 is not
>>> there. This is because clock framework will disable DDR clocks because
>>> there will be no consumer for them.
>>
>> This I understand, but why do you need this patch to be able to apply
>> 1/3?
>
> To avoid having AT91 devices failing to boot in case your tree (containing
> this patch) is merged first.
But this patch is not going to be merged first. It will wait one more
cycle, so the dependency is there.
If you need to make it in one cycle for some reason, then I would need
stable tag with the clock patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-03 13:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:45 [PATCH 0/3] clk: at91: mark ddr clocks as critical Claudiu Beznea
2022-12-08 11:45 ` [PATCH 1/3] " Claudiu Beznea
2023-01-12 10:28 ` Claudiu.Beznea
2022-12-08 11:45 ` [PATCH 2/3] memory: atmel-sdramc: remove the driver Claudiu Beznea
2023-01-03 10:00 ` Claudiu.Beznea
2023-01-03 10:06 ` Krzysztof Kozlowski
2023-01-03 11:18 ` Claudiu.Beznea
2023-01-03 12:00 ` Krzysztof Kozlowski
2023-01-03 12:45 ` Claudiu.Beznea
2023-01-03 13:17 ` Krzysztof Kozlowski [this message]
2023-01-03 14:29 ` Claudiu.Beznea
2022-12-08 11:45 ` [PATCH 3/3] clk: at91: do not compile dt-compat.c for sama7g5 and sam9x60 Claudiu Beznea
2022-12-08 14:39 ` Alexandre Belloni
2022-12-08 15:17 ` Claudiu.Beznea
2023-01-12 10:28 ` Claudiu.Beznea
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=414b2785-fba0-1426-d059-befeabe9ddac@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®