From: Daniel Vetter <daniel@ffwll.ch>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "daniel.vetter@intel.com" <daniel.vetter@intel.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/arcpgu: remove drm_encoder_slave
Date: Tue, 30 Jan 2018 18:07:40 +0100 [thread overview]
Message-ID: <CAKMK7uG_WHFw901n_sO0+LZHrDHJ4XkrsLdakYuSmFB2PJBWLg@mail.gmail.com> (raw)
In-Reply-To: <1517330641.4754.3.camel@synopsys.com>
On Tue, Jan 30, 2018 at 5:44 PM, Alexey Brodkin
<Alexey.Brodkin@synopsys.com> wrote:
> Hi Daniel,
>
> On Tue, 2018-01-30 at 10:15 +0100, Daniel Vetter wrote:
>> On Wed, Jan 17, 2018 at 03:17:55PM +0100, Daniel Vetter wrote:
>> > drm_encoder_slave is the old way to write bridge drivers, for i2c
>> > bridges only. It's deprecated, and definitely should not be used in
>> > new drivers. This has absolutely nothing to do with the new bridge
>> > driver infrastructure implemented by drm_bridge.
>> >
>> > What's even strange is that arcpgu doesn't even use any of this, it
>> > really only wants a plain normal drm_encoder. Nuke all the surplus
>> > real estate.
>> >
>> > v2: Actually git add after compile testing ...
>> >
>> > v3: Clarify commit message and stop including drm_encoder_slave.h.
>> >
>> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>> > Cc: Alexey Brodkin <abrodkin@synopsys.com>
>> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>>
>> I assumed this is ok and applied it to drm-misc-next.
>> -Daniel
>
> Not sure but I still cannot see anything arcpgu-related here
> https://cgit.freedesktop.org/drm-misc/log/
>
> Am I looking at the wrong place?
Build test script got stuck, pushed for real now.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-30 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 13:43 [PATCH] drm/arcpgu: remove drm_encoder_slave Daniel Vetter
2018-01-17 13:53 ` Daniel Vetter
2018-01-17 14:02 ` Laurent Pinchart
2018-01-17 13:55 ` Alexey Brodkin
2018-01-17 14:03 ` Daniel Vetter
2018-01-17 14:17 ` Daniel Vetter
2018-01-30 9:15 ` Daniel Vetter
2018-01-30 16:44 ` Alexey Brodkin
2018-01-30 17:07 ` Daniel Vetter [this message]
2018-01-30 19:06 ` Alexey Brodkin
2018-01-20 1:59 ` kbuild test robot
2018-01-20 4:17 ` kbuild test robot
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=CAKMK7uG_WHFw901n_sO0+LZHrDHJ4XkrsLdakYuSmFB2PJBWLg@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=Alexey.Brodkin@synopsys.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.