dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: airlied@linux.ie, tomi.valkeinen@ti.com,
	dri-devel@lists.freedesktop.org,
	laurent.pinchart@ideasonboard.com, peda@axentia.se
Subject: Re: [PATCH v4 0/2] drm/panel: Add device link in drm_panel_attach()
Date: Thu, 26 Apr 2018 14:49:14 +0200	[thread overview]
Message-ID: <20180426124914.GG11985@ulmo> (raw)
In-Reply-To: <cover.1524727887.git.jsarha@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 438 bytes --]

On Thu, Apr 26, 2018 at 11:06:58AM +0300, Jyri Sarha wrote:
> I guess the first patch should be mergable. With the second, maybe it
> is better to wait until we have a full solution including the bridges
> too. What should I do to get the first patch merged?

I don't see a reason why patch 2 can't be applied as-is right now. The
bridges can always be fixed in a separate patch.

Applied both of these to drm-misc-next, thanks.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-04-26 12:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  8:06 [PATCH v4 0/2] drm/panel: Add device link in drm_panel_attach() Jyri Sarha
2018-04-26  8:06 ` [PATCH v4 1/2] drm/panel: Remove drm_panel_detach() calls from all panel drives Jyri Sarha
2018-04-26  8:07 ` [PATCH v4 2/2] drm/panel: Add device_link from panel device to drm device Jyri Sarha
2018-05-18 11:51   ` Andrzej Hajda
2018-05-18 12:54     ` Jyri Sarha
2018-05-19 16:48     ` Peter Rosin
2018-05-19 18:01       ` Peter Rosin
2018-05-21  8:15       ` Andrzej Hajda
2018-05-21  8:53         ` Peter Rosin
2018-05-21  9:21           ` Andrzej Hajda
2018-05-21 21:56             ` Peter Rosin
2018-05-22  6:29               ` Andrzej Hajda
2018-05-22  7:36                 ` Peter Rosin
2018-05-22  8:37                   ` Peter Rosin
2018-05-22  9:45                   ` Andrzej Hajda
2018-05-22 15:03                     ` Peter Rosin
2018-05-23  8:29                       ` Peter Rosin
2018-05-23  9:39                         ` Andrzej Hajda
2018-05-23 10:46                           ` Peter Rosin
2018-05-23 12:38                             ` Andrzej Hajda
2018-05-23 14:34                               ` Peter Rosin
2019-10-22  8:44     ` Daniel Vetter
2018-08-09  8:56   ` Daniel Vetter
2018-08-30 12:32   ` Linus Walleij
2018-08-30 14:41     ` Andrzej Hajda
2018-08-31  8:56       ` Linus Walleij
2018-08-31 10:08         ` Andrzej Hajda
2018-04-26 12:49 ` Thierry Reding [this message]
2018-05-21  6:09   ` [PATCH v4 0/2] drm/panel: Add device link in drm_panel_attach() 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=20180426124914.GG11985@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=peda@axentia.se \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).