linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	devicetree <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v4 1/7] drm: Add DRM support for tiny LCD displays
Date: Tue, 14 Feb 2017 20:54:28 +0100	[thread overview]
Message-ID: <CAKMK7uF1AYwZGXrpCk01Uy-n8-Wsnr7XX-SxbGgJnMhA28APSw@mail.gmail.com> (raw)
In-Reply-To: <70190e71-4d5a-7102-418f-09896b57c084@tronnes.org>

On Sun, Feb 12, 2017 at 2:57 PM, Noralf Trønnes <noralf@tronnes.org> wrote:
> tinydrm will be merged the way it is now, unless someone points to
> something that is broken. But I collect your comments for a later
> cleanup patchset. It takes a lot of effort for me as an amateur to
> keeps this code up-to-date out-of-tree for months. It's not even
> sure that I've hit the mark with this, so there will most likely be
> changes when I start converting fbtft drivers, and I'll implement the
> remaining bits and pieces as I make changes. The core of tinydrm won't
> change because of unforseen fbtft quirks, but other parts might.

+1, pls send pull request to Dave Airlie. DT-acks are all there, and
Thierry confirmed on irc that his reply on the last thread was indeed
meant as a full ack for going ahead and polishing later. I also
chatted with Dave directly, and he's perfectly happy to take this in
as-is. If you do this soon, should still easily get into 4.11 (since
the 4.10 release is delayed).

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2017-02-14 19:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 18:48 [PATCH v4 0/7] drm: Add support for tiny LCD displays Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 1/7] drm: Add DRM " Noralf Trønnes
2017-02-12 11:05   ` Andy Shevchenko
2017-02-12 13:57     ` Noralf Trønnes
2017-02-14 19:54       ` Daniel Vetter [this message]
2017-03-07 22:21   ` Daniel Vetter
2017-03-08 12:23     ` Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 2/7] drm/tinydrm: Add helper functions Noralf Trønnes
2017-02-12 11:50   ` Andy Shevchenko
2017-02-12 15:33     ` Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 3/7] drm/tinydrm: Add MIPI DBI support Noralf Trønnes
2017-03-12 18:42   ` Daniel Vetter
2017-03-12 19:02     ` Daniel Vetter
2017-02-11 18:48 ` [PATCH v4 4/7] of: Add vendor prefix for Multi-Inno Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 5/7] dt-bindings: display/panel: Add common rotation property Noralf Trønnes
2017-02-14 16:19   ` Rob Herring
2017-04-11  5:29   ` Laurent Pinchart
2017-04-12 11:01     ` Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 6/7] dt-bindings: Add Multi-Inno MI0283QT binding Noralf Trønnes
2017-02-11 18:48 ` [PATCH v4 7/7] drm/tinydrm: Add support for Multi-Inno MI0283QT display Noralf Trønnes

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=CAKMK7uF1AYwZGXrpCk01Uy-n8-Wsnr7XX-SxbGgJnMhA28APSw@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=thomas.petazzoni@free-electrons.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).