From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH v4 0/2] drm/panel: Add device link in drm_panel_attach()
Date: Thu, 26 Apr 2018 14:49:14 +0200
Message-ID: <20180426124914.GG11985@ulmo>
References: <cover.1524727887.git.jsarha@ti.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1340890130=="
Return-path: <dri-devel-bounces@lists.freedesktop.org>
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com
 [IPv6:2a00:1450:400c:c0c::22a])
 by gabe.freedesktop.org (Postfix) with ESMTPS id 773908986D
 for <dri-devel@lists.freedesktop.org>; Thu, 26 Apr 2018 12:49:17 +0000 (UTC)
Received: by mail-wr0-x22a.google.com with SMTP id h3-v6so56681062wrh.5
 for <dri-devel@lists.freedesktop.org>; Thu, 26 Apr 2018 05:49:17 -0700 (PDT)
In-Reply-To: <cover.1524727887.git.jsarha@ti.com>
List-Unsubscribe: <https://lists.freedesktop.org/mailman/options/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <https://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <https://lists.freedesktop.org/mailman/listinfo/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel" <dri-devel-bounces@lists.freedesktop.org>
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
List-Id: dri-devel@lists.freedesktop.org


--===============1340890130==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="gvF4niNJ+uBMJnEh"
Content-Disposition: inline


--gvF4niNJ+uBMJnEh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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

--gvF4niNJ+uBMJnEh
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlrhyskACgkQ3SOs138+
s6GZSA//WLtJK5mmLjEeKjLHQFNRnARbkZZ35yvsU2x+nec6CMhUpWmsxBqHgUgv
cC8luIb0xuyNdflCAL3/yqCZ3dqdqDPRRANvdG8LAhGv2iMv5xlWhVD33XDib3EY
XbsI/r0Ed388+TgFbv+v3XawZLZPuSggujSCxWclUMB49XNFnfVRLdLI0L9F7E5z
rW5F9FR9zowabXZh9iwlZGA8M8QCYk7nZjAZQAAVkZIlmc5zrHtqJxYqr+owDSg1
BhgBSDuMc9y/KS3qvH37QbzcjTuZF2Hv5dueA36BmSDd+kH8NNhlbFaWKU8moGo2
oMlPPgRP2cNtky9SD4IGze1sXVBQzS5m/ZObpvtMt7PHkkzZb2rNKh0JWpwd3EL9
+uMdlWfMFt3nKW/PoSqRXSSp3+mALUygBp0t0MIxnMQypi9QsJsIjgeH52Prrzot
E1dwfPyVDUvdKtUVV8KIEdlVX8BHcb/iMjf+OBUEEeXxowXPmJDJLmiQW+/g2EjD
LCQWYptCbWQyOu8Sz20NO1JqP7y8tJOm7m0BmbrvL6Z4B6fyjRmiEGz3JQS6svY4
YMhtmf2Ge0rgoW6g4iycszT75VbDV92C3ivdypDsXHGcz9Dq2XLcQOvKRGJZg+eN
9H8hfzcZ4n5LnaRetAHevWgg7q9gqu7GJTIaSFkeKZVbkMw14GE=
=Cq7p
-----END PGP SIGNATURE-----

--gvF4niNJ+uBMJnEh--

--===============1340890130==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==

--===============1340890130==--