From: Ruan Jinjie <ruanjinjie@huawei.com>
To: Andi Shyti <andi.shyti@kernel.org>,
<pierre-yves.mordret@foss.st.com>, <alain.volmat@foss.st.com>,
<mcoquelin.stm32@gmail.com>, <alexandre.torgue@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-i2c@vger.kernel.org>
Subject: Re: [PATCH -next] i2c: stm32: fix the return value handle for platform_get_irq()
Date: Sat, 5 Aug 2023 10:44:37 +0800 [thread overview]
Message-ID: <b5fbdc3f-0404-c939-9f33-8d7489c19921@huawei.com> (raw)
In-Reply-To: <169119887102.1781235.17733733758389845864.b4-ty@kernel.org>
On 2023/8/5 9:29, Andi Shyti wrote:
> Hi
>
> On Mon, 31 Jul 2023 19:27:55 +0800, Ruan Jinjie wrote:
>> There is no possible for platform_get_irq() to return 0,
>> and the return value of platform_get_irq() is more sensible
>> to show the error reason.
>>
>>
>
> With the commit log fixed, applied to i2c/andi-for-next on
Thank you!
>
> https://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git
>
> Please note that this patch may still undergo further evaluation
> and the final decision will be made in collaboration with
> Wolfram.
>
> Thank you,
> Andi
>
> Patches applied
> ===============
> [1/1] i2c: stm32: fix the return value handle for platform_get_irq()
> commit: 603b3cf89d8a96cc0e51eb15853f28944eb78f31
>
next prev parent reply other threads:[~2023-08-05 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:27 [PATCH -next] i2c: stm32: fix the return value handle for platform_get_irq() Ruan Jinjie
2023-08-01 23:36 ` Andi Shyti
2023-08-01 23:52 ` Andi Shyti
2023-08-02 1:28 ` Ruan Jinjie
2023-08-02 9:13 ` Alain Volmat
2023-08-05 1:29 ` Andi Shyti
2023-08-05 2:44 ` Ruan Jinjie [this message]
2023-08-14 15:14 ` 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=b5fbdc3f-0404-c939-9f33-8d7489c19921@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andi.shyti@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@foss.st.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