From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] drm/rockchip: lvds: avoid duplicating drm_bridge_attach
Date: Sun, 20 May 2018 13:48:39 +0200 [thread overview]
Message-ID: <2076868.NHBhtu2M9j@phil> (raw)
In-Reply-To: <20180502074025.12421-3-peda@axentia.se>
Am Mittwoch, 2. Mai 2018, 09:40:24 CEST schrieb Peter Rosin:
> drm_bridge_attach takes care of these assignments, so there is no need
> to open-code them a second time.
>
> Signed-off-by: Peter Rosin <peda@axentia.se>
applied to drm-misc-next
Thanks
Heiko
next prev parent reply other threads:[~2018-05-20 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 7:40 [PATCH 0/3] drm: fix some bridge api misunderstandings Peter Rosin
2018-05-02 7:40 ` [PATCH 1/3] drm/sti: do not remove the drm_bridge that was never added Peter Rosin
2018-05-03 9:06 ` Daniel Vetter
2018-05-03 21:12 ` Peter Rosin
2018-05-07 13:39 ` Daniel Vetter
2018-05-07 13:59 ` Peter Rosin
2018-05-07 14:24 ` Peter Rosin
2018-05-08 7:51 ` Daniel Vetter
2018-05-08 7:41 ` Daniel Vetter
2018-05-02 7:40 ` [PATCH 2/3] drm/rockchip: lvds: avoid duplicating drm_bridge_attach Peter Rosin
2018-05-20 11:48 ` Heiko Stuebner [this message]
2018-05-02 7:40 ` [PATCH 3/3] drm/exynos: hdmi: " 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=2076868.NHBhtu2M9j@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).