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-fbdev@vger.kernel.org
Subject: [PATCH] video: don't print error when adding adapter fails
Date: Tue, 09 Aug 2016 11:27:38 +0000 [thread overview]
Message-ID: <1470742059-12341-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 (1):
video: fbdev: mb862xx: mb862xx-i2c: don't print error when adding
adapter fails
drivers/video/fbdev/mb862xx/mb862xx-i2c.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
--
2.8.1
next reply other threads:[~2016-08-09 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:27 Wolfram Sang [this message]
2016-08-09 11:27 ` [PATCH] video: fbdev: mb862xx: mb862xx-i2c: don't print error when adding adapter fails Wolfram Sang
2016-08-10 10:24 ` Tomi Valkeinen
2016-08-10 10:43 ` 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=1470742059-12341-1-git-send-email-wsa-dev@sang-engineering.com \
--to=wsa-dev@sang-engineering.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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).