From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Zhu Wang <wangzhu9@huawei.com>,
gregkh@linuxfoundation.org, herve.codina@bootlin.com,
stern@rowland.harvard.edu, robh@kernel.org, aaro.koskinen@iki.fi,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v3] usb: gadget: udc: gr_udc: Do not check 0 for platform_get_irq()
Date: Thu, 3 Aug 2023 20:00:36 +0300 [thread overview]
Message-ID: <e85efc8e-5a12-5f9f-a23e-d701b5722896@gmail.com> (raw)
In-Reply-To: <20230803121136.86037-1-wangzhu9@huawei.com>
On 8/3/23 3:11 PM, Zhu Wang wrote:
> When platform_get_irq() failed, it may return -EPROBE_DEFER, -EINVAL or
> -ENXIO, it is important to propagate the detail upstream, we cannot
> override it.
Deferred probing being fixed should be emphasized. And the patch is
no longer "-next" material due to that...
> And platform_get_irq() used to return 0 (as both IRQ0 and error
> indication), there are several patches fixing the inconsistencies.
No, this "historical" passage wasn't meant to be a part of the patch
description.
> Commit ce753ad1549c ("platform: finally disallow IRQ0 in
> platform_get_irq() and its ilk") makes sure IRQ0 is not returned.
>
> Signed-off-by: Zhu Wang <wangzhu9@huawei.com>
>
> ---
> Changes in v2:
> - Update the commit message, present the reason of replacing the return
> value of the probe.
>
> ---
> Changes in v3:
> - Update the commit message, explain in detail why the return value of
> platform_get_irq() cannot be override.
As I said, your descrioption isn't very convincing as you don't
emphasize the deferred probing being fixed.
[...]
MBR, Sergey
prev parent reply other threads:[~2023-08-03 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 12:11 Zhu Wang
2023-08-03 17:00 ` Sergei Shtylyov [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=e85efc8e-5a12-5f9f-a23e-d701b5722896@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=wangzhu9@huawei.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®