From: Bastien Nocera <hadess@hadess.net>
To: Wang Yafei <wangyafei@goodix.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
andrew@goodix.com, mouse@goodix.com
Subject: Re: [PATCH] dt-bindings: input: Add the Goodix GTx5 series Touchscreen devicetree bindings
Date: Tue, 20 Jun 2017 11:17:50 +0200 [thread overview]
Message-ID: <1497950270.2559.12.camel@hadess.net> (raw)
In-Reply-To: <20170620085346.GA9345@andrew-dell>
On Tue, 2017-06-20 at 16:53 +0800, Wang Yafei wrote:
> On Tue, Jun 20, 2017 at 12:25:09AM +0200, Bastien Nocera wrote:
> > On Mon, 2017-06-19 at 18:40 +0800, Wang Yafei wrote:
> > > Signed-off-by: Wang Yafei <wangyafei@goodix.com>
> > > ---
> > > .../bindings/input/touchscreen/goodix-gtx5.txt | 75
> > > ++++++++++++++++++++++
> >
> > Where was the driver sent? I didn't see it on linux-input. Why
> > wasn't
> > this support added to the goodix driver instead?
>
> Hi, Bastien,
> I'm sorry for confused you. I have posted two patches one is
> touchscreen
> driver another is this dt-bindings. The driver is under reviewing and
> hasn't
> been applied to linux-input.
But where's the driver? It should have been posted to the linux-input
mailing-list, and I cannot see it there.
> Finally thanks for you advice I'll try add a
> patch in ./bindings/input/touchscreen/goodix.txt rather than add a
> new file.
That's not what I meant. I wonder about the reason why the existing
driver wasn't extended rather than writing a new one.
Good to see that Goodix is finally upstreaming its drivers though, my
attempts at contacting some of your colleagues fell on deaf ears a
couple of years ago.
Cheers
next prev parent reply other threads:[~2017-06-20 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 10:40 [PATCH] dt-bindings: input: Add the Goodix GTx5 series Touchscreen devicetree bindings Wang Yafei
[not found] ` <22592d94-f482-3e4f-3860-1dce83472d4f-PiwChjOeyQzQT0dZR+AlfA@public.gmane.org>
2017-06-19 22:25 ` Bastien Nocera
2017-06-20 8:53 ` Wang Yafei
2017-06-20 9:17 ` Bastien Nocera [this message]
[not found] ` <1497950270.2559.12.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2017-06-20 13:29 ` Wang Yafei
2017-06-23 20:37 ` Rob Herring
2017-06-26 13:22 ` Wang Yafei
2017-06-26 14:16 ` Rob Herring
[not found] ` <CAL_JsqJ6w7oEjm=i_KX8Y_axbRSdX4Q+14NQ8XaHnDevGQrS_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-27 3:14 ` Wang Yafei
2017-06-27 3:27 ` Wang Yafei
2017-06-30 14:46 ` Rob Herring
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=1497950270.2559.12.camel@hadess.net \
--to=hadess@hadess.net \
--cc=andrew@goodix.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mouse@goodix.com \
--cc=robh+dt@kernel.org \
--cc=wangyafei@goodix.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).