From: Thierry Reding <thierry.reding@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] display: panel: Add Tianma tm070rvhg71 display support (800x480)
Date: Fri, 17 Nov 2017 13:27:13 +0100 [thread overview]
Message-ID: <20171117122713.GA22989@ulmo> (raw)
In-Reply-To: <20171117131712.0f2a0a4f@jawa>
[-- Attachment #1.1: Type: text/plain, Size: 1497 bytes --]
On Fri, Nov 17, 2017 at 01:17:12PM +0100, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Fri, Nov 17, 2017 at 11:02:47AM +0100, Lukasz Majewski wrote:
> > > Dear All,
> > >
> > > > On Tue, Nov 07, 2017 at 04:30:58PM +0100, Lukasz Majewski wrote:
> > > > > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > > > >
> > > > > ---
> > > > > Changes for v2:
> > > > > - Provide more
> > > > > detailed ./Documentation/devicetree/bindings/display/panel
> > > > > entry to describe this panel device. ---
> > > > > .../bindings/display/panel/tianma,tm070rvhg71.txt | 29
> > > > > ++++++++++++++++++++++
> > > > > drivers/gpu/drm/panel/panel-simple.c | 27
> > > > > ++++++++++++++++++++ 2 files changed, 56 insertions(+) create
> > > > > mode 100644
> > > > > Documentation/devicetree/bindings/display/panel/tianma,tm070rvhg71.txt
> > > >
> > > > Acked-by: Rob Herring <robh@kernel.org>
> > >
> > > Is there a chance that this patch will find its way to v4.15-rc1 ?
> >
> > No, that's very unlikely. We're in the middle of the merge window, no
> > new patches are accepted at that point.
>
> Ok. I see. I should have sent the ping earlier.
Looking at the timeline of this patch even that wouldn't have been
enough. You sent the original patch on October 21, which is one day
after the final drm-misc feature pull request was tagged. So this
wouldn't have made it into v4.15-rc1 no matter how early you would
have pinged. =)
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
next prev parent reply other threads:[~2017-11-17 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 22:10 [PATCH] display: panel: Add Tianma tm070rvhg71 display support (800x480) Lukasz Majewski
[not found] ` <1508537403-878-1-git-send-email-lukma-ynQEQJNshbs@public.gmane.org>
2017-10-27 3:13 ` Rob Herring
2017-10-27 8:18 ` Lukasz Majewski
2017-11-05 22:19 ` Lukasz Majewski
2017-11-06 14:30 ` Rob Herring
2017-11-07 15:30 ` [PATCH v2] " Lukasz Majewski
[not found] ` <20171107153058.5554-1-lukma-ynQEQJNshbs@public.gmane.org>
2017-11-10 21:24 ` Rob Herring
2017-11-17 10:02 ` Lukasz Majewski
2017-11-17 11:41 ` Thierry Reding
2017-11-17 12:17 ` Lukasz Majewski
2017-11-17 12:27 ` Thierry Reding [this message]
2017-11-17 12:29 ` Lukasz Majewski
2017-11-17 11:36 ` Thierry Reding
2017-11-17 12:14 ` Lukasz Majewski
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=20171117122713.GA22989@ulmo \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=mark.rutland@arm.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).