mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Starkey <brian.starkey@arm.com>
To: Russell King <rmk+kernel@armlinux.org.uk>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: jsarha@ti.com
Subject: Re: [PATCH] drm: tda998x: mali-dp: hdlcd: refactor connector registration
Date: Tue, 25 Oct 2016 11:40:59 +0100	[thread overview]
Message-ID: <20161025104059.GE1988@e106950-lin.cambridge.arm.com> (raw)
In-Reply-To: <20161025101919.35c53zoyf435urp3@phenom.ffwll.local>

On Tue, Oct 25, 2016 at 12:19:19PM +0200, Daniel Vetter wrote:
>On Tue, Oct 25, 2016 at 10:52:33AM +0100, Brian Starkey wrote:
>
>Ah, makes sense. Should I apply this to drm-misc so it's in a shared tree?

Honestly, I don't know. I didn't entirely follow what it was Russell
wanted in terms of getting this merged:

>On Sat, Oct 22, 2016 at 02:40:22PM +0100, Russell King - ARM Linux wrote:
>>So, what I would like to see is a single patch against Linus' 4.8.0
>>commit fixing mali-dp, hdlcd and any other driver, together with
>>removing drm_connector_register() from TDA998x.  This is so the patch
>>can be shared between all interested parties without forcing everyone
>>to 4.9-rc1.  Looking at the diff between 4.8 and 4.9-rc1 for
>>drivers/gpu/drm/arm, that shouldn't result in any merge conflicts -
>>and if you want to follow on from that with 4.9-rc1 development, you
>>can always merge 4.9-rc1 on top of that commit.

Looks like Jyri's series which depends on this is also dependent on
Russell's tree, so might be best to wait for him to get back online.

-Brian

>-Daniel
>-- 
>Daniel Vetter
>Software Engineer, Intel Corporation
>http://blog.ffwll.ch
>

  reply	other threads:[~2016-10-25 10:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161024142312.GA1988@e106950-lin.cambridge.arm.com>
2016-10-24 14:27 ` Brian Starkey
2016-10-24 14:36   ` Daniel Vetter
2016-10-24 14:52     ` Brian Starkey
2016-10-24 20:24       ` Daniel Vetter
2016-10-25  9:52         ` Brian Starkey
2016-10-25 10:19           ` Daniel Vetter
2016-10-25 10:40             ` Brian Starkey [this message]
2016-10-31  9:00             ` Russell King - ARM Linux
2016-10-31 10:16               ` Russell King - ARM Linux
2016-10-31  8:58         ` Russell King - ARM Linux
2016-11-08  9:25           ` Daniel Vetter
2016-11-08 10:59             ` Russell King - ARM Linux
2016-11-08 11:27               ` Daniel Vetter
2016-11-15  9:46               ` [GIT PULL] " Russell King - ARM Linux
2016-11-16 21:31                 ` Russell King - ARM Linux

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=20161025104059.GE1988@e106950-lin.cambridge.arm.com \
    --to=brian.starkey@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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

all inboxes | Powered by JetHome®