From: Wolfram Sang <wsa@the-dreams.de>
To: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: o.rempel@pengutronix.de, u.kleine-koenig@pengutronix.de,
ardb@kernel.org, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Shengju Zhang <zhangshengju@cmss.chinamobile.com>
Subject: Re: [PATCH] i2c: drivers: Omit superfluous error message in efm32_i2c_probe()
Date: Fri, 22 May 2020 17:04:18 +0200 [thread overview]
Message-ID: <20200522150418.GG5670@ninjato> (raw)
In-Reply-To: <20200415135734.14660-1-tangbin@cmss.chinamobile.com>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Wed, Apr 15, 2020 at 09:57:34PM +0800, Tang Bin wrote:
> In the function efm32_i2c_probe(),when get irq failed,the function
> platform_get_irq() logs an error message,so remove redundant message
> here.
>
> Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
> Signed-off-by: Shengju Zhang <zhangshengju@cmss.chinamobile.com>
Applied to for-next, thanks! Please fix the issues Uwe mentioned next
time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: linux-kernel@vger.kernel.org,
Shengju Zhang <zhangshengju@cmss.chinamobile.com>,
o.rempel@pengutronix.de, linux-i2c@vger.kernel.org,
u.kleine-koenig@pengutronix.de, ardb@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: drivers: Omit superfluous error message in efm32_i2c_probe()
Date: Fri, 22 May 2020 17:04:18 +0200 [thread overview]
Message-ID: <20200522150418.GG5670@ninjato> (raw)
In-Reply-To: <20200415135734.14660-1-tangbin@cmss.chinamobile.com>
[-- Attachment #1.1: Type: text/plain, Size: 422 bytes --]
On Wed, Apr 15, 2020 at 09:57:34PM +0800, Tang Bin wrote:
> In the function efm32_i2c_probe(),when get irq failed,the function
> platform_get_irq() logs an error message,so remove redundant message
> here.
>
> Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
> Signed-off-by: Shengju Zhang <zhangshengju@cmss.chinamobile.com>
Applied to for-next, thanks! Please fix the issues Uwe mentioned next
time.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2020-05-22 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:57 [PATCH] i2c: drivers: Omit superfluous error message in efm32_i2c_probe() Tang Bin
2020-04-15 13:57 ` Tang Bin
2020-04-15 14:22 ` Uwe Kleine-König
2020-04-15 14:22 ` Uwe Kleine-König
2020-04-16 1:12 ` [PATCH] i2c: drivers: Omit superfluous error message inefm32_i2c_probe() Tang Bin
2020-04-16 1:12 ` Tang Bin
2020-05-22 15:04 ` Wolfram Sang [this message]
2020-05-22 15:04 ` [PATCH] i2c: drivers: Omit superfluous error message in efm32_i2c_probe() Wolfram Sang
2020-05-22 15:09 ` Wolfram Sang
2020-05-22 15:09 ` 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=20200522150418.GG5670@ninjato \
--to=wsa@the-dreams.de \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=tangbin@cmss.chinamobile.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhangshengju@cmss.chinamobile.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.