mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	linux-kernel@vger.kernel.org,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the fallback
Date: Mon, 3 Nov 2025 16:12:51 +0100	[thread overview]
Message-ID: <e1fd975c-56ef-442b-8617-d63237bf795a@linaro.org> (raw)
In-Reply-To: <20251015205919.12678-4-wsa+renesas@sang-engineering.com>

On 15/10/2025 22:59, Wolfram Sang wrote:
> After the discussion[1] (Thanks, Philipp!), here is the updated series.
> Details are in the commit messages. Please let me know what you think.
> 
> [1] https://lore.kernel.org/r/20251015112921.19535-2-wsa+renesas@sang-engineering.com
> 

You removed RFC and entire rationale. Your earlier commit - 690de2902dca
- is broken. You must not do that. Broken 690de2902dca leads to this
broken patchset, but that is not a correct fix. You need to fix the
source - revert 690de2902dca, because it is obviously wrong. You MUST
ave fallback to reset-gpios, that was the entire concept how this driver
was written.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-11-03 15:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 20:59 Wolfram Sang
2025-10-15 20:59 ` [PATCH v2 1/2] reset: always bail out on missing RESET_GPIO driver Wolfram Sang
2025-10-17  9:35   ` Philipp Zabel
2025-10-30 11:59   ` Philipp Zabel
2025-10-30 12:54   ` Philipp Zabel
2025-11-03 14:53     ` Krzysztof Kozlowski
2025-11-03 15:12       ` Wolfram Sang
2025-11-03 15:13         ` Krzysztof Kozlowski
2025-11-03 17:10   ` Wolfram Sang
2025-10-15 20:59 ` [PATCH v2 2/2] reset: always include RESET_GPIO driver if possible Wolfram Sang
2025-10-16 13:02   ` Geert Uytterhoeven
2025-10-16 14:27     ` Wolfram Sang
2025-10-17 10:16       ` Bartosz Golaszewski
2025-10-17 10:48         ` Wolfram Sang
2025-10-17 11:09           ` Bartosz Golaszewski
2025-10-17 11:25             ` Wolfram Sang
2025-10-17 17:02               ` Bartosz Golaszewski
2025-10-22  9:07                 ` Philipp Zabel
2025-10-23  9:22                   ` Wolfram Sang
2025-10-23  9:37                     ` Bartosz Golaszewski
2025-10-23 11:18                       ` Wolfram Sang
2025-10-23 12:04                         ` Bartosz Golaszewski
2025-10-23 12:51                           ` Wolfram Sang
2025-10-17  9:42     ` Philipp Zabel
2025-10-17  9:46       ` Wolfram Sang
2025-10-17  9:35   ` Philipp Zabel
2025-10-17  9:43     ` Wolfram Sang
2025-10-16  0:02 ` [PATCH v2 0/2] reset: handle RESET_GPIO better to provide the fallback Kuninori Morimoto
2025-11-03 15:08   ` Krzysztof Kozlowski
2025-11-03 15:25     ` Wolfram Sang
2025-11-03 15:26       ` Krzysztof Kozlowski
2025-11-03 15:12 ` Krzysztof Kozlowski [this message]
2025-11-03 15:23   ` Wolfram Sang
2025-11-03 15:26     ` Krzysztof Kozlowski
2025-11-03 15:52       ` Wolfram Sang

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=e1fd975c-56ef-442b-8617-d63237bf795a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=wsa+renesas@sang-engineering.com \
    /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®