From: Andi Shyti <andi.shyti@kernel.org>
To: brgl@bgdev.pl, conor.dooley@microchip.com,
daire.mcnamara@microchip.com,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-riscv@lists.infradead.org, Zhu Wang <wangzhu9@huawei.com>
Cc: Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH -next v2] i2c: remove redundant dev_err_probe()
Date: Wed, 2 Aug 2023 22:10:36 +0200 [thread overview]
Message-ID: <169100562785.1919254.291391952713888023.b4-ty@kernel.org> (raw)
In-Reply-To: <20230801134814.247782-1-wangzhu9@huawei.com>
Hi
On Tue, 01 Aug 2023 21:48:14 +0800, Zhu Wang wrote:
> When platform_get_irq() is called, the error message has been printed,
> so it need not to call dev_err_probe() to print error.
>
> As the comment of platform_get_irq() says, it returned non-zero value
> when it succeeded, and it returned negative value when it failed.
>
>
> [...]
Applied to i2c/andi-for-next on
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: remove redundant dev_err_probe()
commit: 6a07ab839a9c14df82ba2fe0b5dd4faa85a64d89
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-02 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 13:48 [PATCH -next v2] i2c: remove redundant dev_err_probe() Zhu Wang
2023-08-02 20:10 ` Andi Shyti [this message]
2023-08-14 15:11 ` 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=169100562785.1919254.291391952713888023.b4-ty@kernel.org \
--to=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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