From: "Heiko Stübner" <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux-rockchip@lists.infradead.org,
Alexandru Stan <amstan@chromium.org>,
briannorris@chromium.org, ykk@rock-chips.com,
mark.yao@rock-chips.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add ddc i2c reference to veyron
Date: Sun, 13 Sep 2015 14:23:39 +0200 [thread overview]
Message-ID: <1633680.4IzccqHRpx@diego> (raw)
In-Reply-To: <1441229148-12095-1-git-send-email-dianders@chromium.org>
Am Mittwoch, 2. September 2015, 14:25:48 schrieb Douglas Anderson:
> The ddc-i2c-bus property was missing from the veyron dtsi file since
> downstream the ddc-i2c-bus was still being specified in rk3288.dtsi and
> nobody noticed when the veyron dtsi was sent upstream. Add it.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
I've applied that to a dts-fixes branch for 4.3 with Brian's Tested-by tag.
As discussed this is temporary-only anyway till the internal i2c stuff of the
dw_hdmi works.
Heiko
prev parent reply other threads:[~2015-09-13 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 21:25 Douglas Anderson
2015-09-03 0:13 ` Rob Herring
2015-09-03 0:22 ` Doug Anderson
2015-09-03 8:22 ` Russell King - ARM Linux
2015-09-03 14:46 ` Rob Herring
2015-09-03 15:18 ` Russell King - ARM Linux
2015-09-03 15:46 ` Rob Herring
2015-09-03 16:04 ` Doug Anderson
2015-09-03 16:13 ` Lucas Stach
2015-09-03 16:28 ` Doug Anderson
2015-09-03 15:55 ` Doug Anderson
2015-09-03 21:00 ` Doug Anderson
2015-09-03 22:01 ` Heiko Stuebner
2015-09-03 22:56 ` Brian Norris
2015-09-13 12:23 ` Heiko Stübner [this message]
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=1633680.4IzccqHRpx@diego \
--to=heiko@sntech.de \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ykk@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome