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>,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: [PATCH 0/5] gpu: don't print error when adding adapter fails
Date: Tue, 9 Aug 2016 13:30:26 +0200 [thread overview]
Message-ID: <1470742232-12559-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 (5):
gpu: drm: amd: amdgpu: amdgpu_i2c: don't print error when adding
adapter fails
gpu: drm: mediatek: mtk_hdmi_ddc: don't print error when adding
adapter fails
gpu: drm: msm: hdmi: hdmi_i2c: don't print error when adding adapter
fails
gpu: drm: radeon: radeon_i2c: don't print error when adding adapter
fails
gpu: drm: rockchip: inno_hdmi: don't print error when adding adapter
fails
drivers/gpu/drm/amd/amdgpu/amdgpu_i2c.c | 4 +---
drivers/gpu/drm/mediatek/mtk_hdmi_ddc.c | 4 +---
drivers/gpu/drm/msm/hdmi/hdmi_i2c.c | 5 +----
drivers/gpu/drm/radeon/radeon_i2c.c | 8 ++------
drivers/gpu/drm/rockchip/inno_hdmi.c | 1 -
5 files changed, 5 insertions(+), 17 deletions(-)
--
2.8.1
next reply other threads:[~2016-08-09 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:30 Wolfram Sang [this message]
2016-08-09 11:30 ` [PATCH 1/5] gpu: drm: amd: amdgpu: amdgpu_i2c: don't print error when adding adapter fails Wolfram Sang
2016-08-09 11:30 ` [PATCH 2/5] gpu: drm: mediatek: mtk_hdmi_ddc: " Wolfram Sang
2016-08-09 11:30 ` [PATCH 3/5] gpu: drm: msm: hdmi: hdmi_i2c: " Wolfram Sang
2016-08-09 11:30 ` [PATCH 4/5] gpu: drm: radeon: radeon_i2c: " Wolfram Sang
2016-08-10 18:10 ` Alex Deucher
2016-08-09 11:30 ` [PATCH 5/5] gpu: drm: rockchip: inno_hdmi: " 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=1470742232-12559-1-git-send-email-wsa-dev@sang-engineering.com \
--to=wsa-dev@sang-engineering.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@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 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).