From: Wolfram Sang <wsa@kernel.org>
To: Aishwarya Ramakrishnan <aishwaryarj100@gmail.com>
Cc: Thor Thayer <thor.thayer@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Vladimir Zapolskiy <vz@mleia.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pierre-Yves MORDRET <pierre-yves.mordret@st.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Baruch Siach <baruch@tkos.co.il>,
Dmitry Osipenko <digetx@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: drivers: Remove superfluous error message
Date: Tue, 5 May 2020 16:13:16 +0200 [thread overview]
Message-ID: <20200505141316.GB2468@ninjato> (raw)
In-Reply-To: <20200504114408.9128-1-aishwaryarj100@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
On Mon, May 04, 2020 at 05:14:06PM +0530, Aishwarya Ramakrishnan wrote:
> The function platform_get_irq can log an error by itself.
> This omit a redundant message for exception handling in the
> calling function.
>
> Suggested by Coccinelle.
>
> Signed-off-by: Aishwarya Ramakrishnan <aishwaryarj100@gmail.com>
Sorry, I forgot that these are already fixed with
e42688ed5cf5936fb55c78cc365dbe0944af7c63 in i2c/for-next.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-05-05 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 12:08 [PATCH] i2c: uniphier: Remove superfluous error message in uniphier_i2c_probe() Aishwarya Ramakrishnan
2020-05-03 13:29 ` Wolfram Sang
2020-05-04 0:15 ` Masahiro Yamada
2020-05-04 11:44 ` [PATCH] i2c: drivers: Remove superfluous error message Aishwarya Ramakrishnan
2020-05-04 12:42 ` Andy Shevchenko
2020-05-04 12:44 ` Andy Shevchenko
2020-05-04 14:30 ` Masahiro Yamada
2020-05-05 14:13 ` Wolfram Sang [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=20200505141316.GB2468@ninjato \
--to=wsa@kernel.org \
--cc=aishwaryarj100@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baruch@tkos.co.il \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-yves.mordret@st.com \
--cc=tglx@linutronix.de \
--cc=thor.thayer@linux.intel.com \
--cc=vz@mleia.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).