From: Krzysztof Kozlowski <krzk@kernel.org>
To: shao.mingyin@zte.com.cn, linux-gpio@vger.kernel.org
Cc: linusw@kernel.org, brgl@kernel.org, linux-kernel@vger.kernel.org,
andrew@codeconstruct.com.au, wbg@kernel.org,
florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, jelonek.jonas@gmail.com
Subject: Re: [PATCH v2 1/4] gpio: aspeed-sgpio: propagate IRQ setup error in probe
Date: Mon, 16 Nov 2026 10:44:44 +0100 [thread overview]
Message-ID: <0ee712ec-438f-4943-8936-6d40d0c923a8@kernel.org> (raw)
In-Reply-To: <20261116172220285RZF6Zcof9cL_fYGhfKKyA@zte.com.cn>
On 16/11/2026 10:22, shao.mingyin@zte.com.cn wrote:
> Hi Krzysztof,
>
> Thank you for the direct reply. You are right about the patch, and you
> are right about the wider pattern. I was wrong on both, and I am
> responsible for them.
>
> I cannot show how the parent interrupt controller could defer probing,
> and stable was not justified for this change. I should have established
> that before sending it. I am withdrawing it (v2 1/4); there will be no
> v3.
That's LLM reply, just like many of others. I am not wasting time on
talking to LLMs through a proxy.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-16 9:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:28 [PATCH v2 0/4] gpio: fix IRQ handling and probe error paths in four drivers shao.mingyin
2026-11-10 15:29 ` [PATCH v2 1/4] gpio: aspeed-sgpio: propagate IRQ setup error in probe shao.mingyin
2026-11-16 8:02 ` Krzysztof Kozlowski
2026-11-16 9:22 ` shao.mingyin
2026-11-16 9:44 ` Krzysztof Kozlowski [this message]
2026-11-10 15:29 ` [PATCH v2 2/4] gpio: 104-idi-48: fix max_register blocking the IRQ register shao.mingyin
2026-11-10 15:29 ` [PATCH v2 3/4] gpio: brcmstb: don't turn platform_get_irq errors into -ENOENT shao.mingyin
2026-11-10 15:29 ` [PATCH v2 4/4] gpio: line-mux: fix unsigned truncation of property count error shao.mingyin
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=0ee712ec-438f-4943-8936-6d40d0c923a8@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brgl@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jelonek.jonas@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=wbg@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®