From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 24/26] drm/bridge: remove the .of_node member
Date: Sat, 19 May 2018 18:08:30 +0200 [thread overview]
Message-ID: <5194502.mIuqRB9jFM@phil> (raw)
In-Reply-To: <20180516101510.13215-25-peda@axentia.se>
Am Mittwoch, 16. Mai 2018, 12:15:08 CEST schrieb Peter Rosin:
> It is unused.
>
> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Peter Rosin <peda@axentia.se>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_lvds.c b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> index 557e0079c98d..e77d4c909582 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_lvds.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> @@ -377,8 +377,6 @@ static int rockchip_lvds_bind(struct device *dev, struct device *master,
> }
> if (lvds->panel)
> remote = lvds->panel->dev->of_node;
> - else if (lvds->bridge->of_node)
> - remote = lvds->bridge->of_node;
> else
> remote = lvds->bridge->odev->of_node;
> if (of_property_read_string(dev->of_node, "rockchip,output", &name))
for the Rockchip-part
Acked-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2018-05-19 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 10:14 [PATCH v3 00/26] device link, bridge supplier <-> drm device Peter Rosin
2018-05-16 10:14 ` [PATCH v3 01/26] drm/bridge: allow optionally specifying an owner .odev device Peter Rosin
2018-05-19 16:07 ` Heiko Stuebner
2018-05-16 10:15 ` [PATCH v3 19/26] drm/exynos: mic: provide an owner .odev device for the bridge Peter Rosin
2018-05-16 10:15 ` [PATCH v3 20/26] drm/mediatek: hdmi: " Peter Rosin
2018-05-16 10:22 ` Philipp Zabel
2018-05-16 10:15 ` [PATCH v3 24/26] drm/bridge: remove the .of_node member Peter Rosin
2018-05-19 16:08 ` Heiko Stuebner [this message]
2018-05-16 10:15 ` [PATCH v3 25/26] drm/bridge: require the owner .odev to be filled in on drm_bridge_add/attach Peter Rosin
2018-05-16 10:15 ` [PATCH v3 26/26] drm/bridge: establish a link between the bridge supplier and consumer Peter Rosin
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=5194502.mIuqRB9jFM@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@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).