From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: linux-kernel@vger.kernel.org
Cc: linux-i2c@vger.kernel.org,
Wolfram Sang <wsa-dev@sang-engineering.com>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: [PATCH 0/4] media: don't print error when adding adapter fails
Date: Tue, 9 Aug 2016 13:35:12 +0200 [thread overview]
Message-ID: <1470742517-12774-1-git-send-email-wsa-dev@sang-engineering.com> (raw)
Since v4.8-rc1, the I2C core will print detailed information when adding an I2C
adapter fails. So, drivers can skip this now.
Should go via subsystem tree, I'd think.
Wolfram Sang (4):
media: pci: netup_unidvb: don't print error when adding adapter fails
media: pci: pt3: don't print error when adding adapter fails
media: platform: exynos4-is: fimc-is-i2c: don't print error when
adding adapter fails
media: usb: dvb-usb-v2: dvb_usb_core: don't print error when adding
adapter fails
drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c | 5 +----
drivers/media/pci/pt3/pt3.c | 4 +---
drivers/media/platform/exynos4-is/fimc-is-i2c.c | 5 +----
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c | 2 --
4 files changed, 3 insertions(+), 13 deletions(-)
--
2.8.1
next reply other threads:[~2016-08-09 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:35 Wolfram Sang [this message]
2016-08-09 11:35 ` [PATCH 1/4] media: pci: netup_unidvb: don't print error when adding adapter fails Wolfram Sang
[not found] ` <CAK3bHNWmxQsAtefcUocoOcEwtWnpptiVxzhXR-+jVU524RmnPw@mail.gmail.com>
2016-08-09 14:58 ` Wolfram Sang
2016-08-10 14:41 ` Abylay Ospan
2016-08-10 14:56 ` Wolfram Sang
2016-08-10 15:06 ` Abylay Ospan
2016-08-09 11:35 ` [PATCH 2/4] media: pci: pt3: " Wolfram Sang
2016-08-09 11:35 ` [PATCH 3/4] media: platform: exynos4-is: fimc-is-i2c: " Wolfram Sang
2016-08-09 11:35 ` [PATCH 4/4] media: usb: dvb-usb-v2: dvb_usb_core: " 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=1470742517-12774-1-git-send-email-wsa-dev@sang-engineering.com \
--to=wsa-dev@sang-engineering.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.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 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).