From: wsa@the-dreams.de (Wolfram Sang)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] i2c: don't print error when adding adapter fails
Date: Mon, 15 Aug 2016 00:17:20 +0200 [thread overview]
Message-ID: <20160814221719.GA10501@katana> (raw)
In-Reply-To: <1470742581-12971-1-git-send-email-wsa-dev@sang-engineering.com>
On Tue, Aug 09, 2016 at 01:36:16PM +0200, Wolfram Sang wrote:
> Since v4.8-rc1, the I2C core will print detailed information when adding an I2C
> adapter fails. So, drivers can skip this now.
>
> I am still undecided if I apply this as a single patch or break it out. But for
> reviewing, avoiding the patch bomb is probably a good thing.
>
> Should go via subsystem tree, I'd think.
>
> Wolfram Sang (1):
> i2c: don't print error when adding adapter fails
>
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20160815/1ec8f886/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Wolfram Sang <wsa-dev@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
adi-buildroot-devel@lists.sourceforge.net, kernel@stlinux.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] i2c: don't print error when adding adapter fails
Date: Mon, 15 Aug 2016 00:17:20 +0200 [thread overview]
Message-ID: <20160814221719.GA10501@katana> (raw)
In-Reply-To: <1470742581-12971-1-git-send-email-wsa-dev@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Tue, Aug 09, 2016 at 01:36:16PM +0200, Wolfram Sang wrote:
> Since v4.8-rc1, the I2C core will print detailed information when adding an I2C
> adapter fails. So, drivers can skip this now.
>
> I am still undecided if I apply this as a single patch or break it out. But for
> reviewing, avoiding the patch bomb is probably a good thing.
>
> Should go via subsystem tree, I'd think.
>
> Wolfram Sang (1):
> i2c: don't print error when adding adapter fails
>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: don't print error when adding adapter fails
Date: Mon, 15 Aug 2016 00:17:20 +0200 [thread overview]
Message-ID: <20160814221719.GA10501@katana> (raw)
In-Reply-To: <1470742581-12971-1-git-send-email-wsa-dev@sang-engineering.com>
On Tue, Aug 09, 2016 at 01:36:16PM +0200, Wolfram Sang wrote:
> Since v4.8-rc1, the I2C core will print detailed information when adding an I2C
> adapter fails. So, drivers can skip this now.
>
> I am still undecided if I apply this as a single patch or break it out. But for
> reviewing, avoiding the patch bomb is probably a good thing.
>
> Should go via subsystem tree, I'd think.
>
> Wolfram Sang (1):
> i2c: don't print error when adding adapter fails
>
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160815/1ec8f886/attachment.sig>
next prev parent reply other threads:[~2016-08-14 22:17 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:36 [PATCH] i2c: don't print error when adding adapter fails Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:36 ` Wolfram Sang
2016-08-09 11:47 ` Grygorii Strashko
2016-08-09 11:47 ` Grygorii Strashko
2016-08-09 11:47 ` Grygorii Strashko
2016-08-09 11:48 ` Peter Korsgaard
2016-08-09 11:48 ` Peter Korsgaard
2016-08-09 11:48 ` Peter Korsgaard
2016-08-09 11:57 ` Uwe Kleine-König
2016-08-09 11:57 ` Uwe Kleine-König
2016-08-09 11:57 ` Uwe Kleine-König
2016-08-09 13:59 ` Wolfram Sang
2016-08-09 13:59 ` Wolfram Sang
2016-08-09 13:59 ` Wolfram Sang
2016-08-09 12:13 ` Heiko Stübner
2016-08-09 12:13 ` Heiko Stübner
2016-08-09 12:13 ` Heiko Stübner
2016-08-09 12:55 ` Neil Horman
2016-08-09 12:55 ` Neil Horman
2016-08-09 12:55 ` Neil Horman
2016-08-10 2:56 ` Zhang, Sonic
2016-08-10 2:56 ` Zhang, Sonic
2016-08-10 2:56 ` Zhang, Sonic
2016-08-09 12:58 ` Thierry Reding
2016-08-09 12:58 ` Thierry Reding
2016-08-09 12:58 ` Thierry Reding
2016-08-09 13:31 ` Guenter Roeck
2016-08-09 13:31 ` Guenter Roeck
2016-08-09 13:31 ` Guenter Roeck
2016-08-09 14:39 ` Wolfram Sang
2016-08-09 14:39 ` Wolfram Sang
2016-08-09 14:39 ` Wolfram Sang
2016-08-09 16:15 ` Ray Jui
2016-08-09 16:15 ` Ray Jui
2016-08-09 16:15 ` Ray Jui
2016-08-09 16:36 ` Vladimir Zapolskiy
2016-08-09 16:36 ` Vladimir Zapolskiy
2016-08-09 16:36 ` Vladimir Zapolskiy
2016-08-10 6:17 ` Ludovic Desroches
2016-08-10 6:17 ` Ludovic Desroches
2016-08-10 6:17 ` Ludovic Desroches
2016-08-10 8:32 ` Krzysztof Kozlowski
2016-08-10 8:32 ` Krzysztof Kozlowski
2016-08-10 8:32 ` Krzysztof Kozlowski
2016-08-10 8:34 ` Laxman Dewangan
2016-08-10 8:34 ` Laxman Dewangan
2016-08-10 8:34 ` Laxman Dewangan
2016-10-05 15:17 ` Jean Delvare
2016-10-05 15:17 ` Jean Delvare
2016-10-05 15:17 ` Jean Delvare
2016-08-09 16:45 ` Joachim Eastwood
2016-08-09 16:45 ` Joachim Eastwood
2016-08-09 16:45 ` Joachim Eastwood
2016-08-09 16:45 ` Joachim Eastwood
2016-08-10 6:50 ` [STLinux Kernel] " Patrice Chotard
2016-08-10 6:50 ` Patrice Chotard
2016-08-10 6:50 ` Patrice Chotard
2016-08-10 6:50 ` Patrice Chotard
2016-08-14 22:17 ` Wolfram Sang [this message]
2016-08-14 22:17 ` Wolfram Sang
2016-08-14 22:17 ` 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=20160814221719.GA10501@katana \
--to=wsa@the-dreams.de \
--cc=linus-amlogic@lists.infradead.org \
/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.