From: "benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>
To: Yuta Kobayashi <alu.ula@outlook.com>
Cc: Jiri Kosina <jikos@kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH] HID: multitouch: enable the Surface 4 Type Cover Pro (JP) to report multitouch data
Date: Fri, 16 Dec 2016 09:10:11 +0100 [thread overview]
Message-ID: <20161216081011.GF31881@mail.corp.redhat.com> (raw)
In-Reply-To: <OSXPR01MB0791665ABC048023FE1E653EF29C0@OSXPR01MB0791.jpnprd01.prod.outlook.com>
Hi,
On Dec 16 2016 or thereabouts, Yuta Kobayashi wrote:
> Thank you for advice.
>
> I found this thread.
> http://www.spinics.net/lists/linux-input/msg48065.html
>
> I think special drivers for Type Cover will not be needed by the patches.
> So i removed some defines such as patch below.
> http://www.spinics.net/lists/linux-input/msg48068.html
>
> Will not this be ground?
>
> If so, my idea is just wrong, sorry.
Actually, your idea is right. The thing Jiri is asking is just a small
paragraph in the patch explaining why this is required. Both Jiri and I
know this is the good approach but it is purely for documentation
purpose.
Something along the lines would be:
---
Since commit 8fe89ef076fa1 ("HID: multitouch: enable the Surface 3 Type
Cover to report multitouch data"), the TypeCover can be properly handled
by hid-multitouch and don't require any special quirk in the kernel.
Remove the support of the Surface 4 Type Cover Pro (JP) from
hid-microsoft so it can properly report multitouch from the touchpad.
---
Add this paragraph below a blank line after the title of the commit and
before your signed-off-by and my reviewed-by, resubmit and we are good
to go.
Cheers,
Benjamin
>
> Thanks.
>
> 2016-12-16 15:46 GMT+09:00 Yuta Kobayashi <alu.ula@outlook.com>:
> > On Thu, 15 Dec 2016, benjamin.tissoires@redhat.com wrote:
> >
> >> On Dec 15 2016 or thereabouts, Yuta Kobayashi wrote:
> >> > From: Yuta Kobayashi <alu.ula@outlook.com>
> >> >
> >> > Signed-off-by: Yuta Kobayashi <alu.ula@outlook.com>
> >> > ---
> >> > drivers/hid/hid-core.c | 2 --
> >> > drivers/hid/hid-ids.h | 1 -
> >> > drivers/hid/hid-microsoft.c | 2 --
> >> > drivers/hid/usbhid/hid-quirks.c | 1 -
> >> > 4 files changed, 6 deletions(-)
> >>
> >> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> >
> > Thanks. I still have one request though -- Yuta-san, could you please
> > resend the patch with a brief description in the patch changelog (what the
> > patch is achieving and why this way is the correct way to do so).
> >
> > We generally want brief description even for the simpliest changes;
> > future will be grateful.
> >
> > Thanks,
> >
> > --
> > Jiri Kosina
> > SUSE Labs
> >
next prev parent reply other threads:[~2016-12-16 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OSXPR01MB0791C4F683C0E619C7660BEEF29D0@OSXPR01MB0791.jpnprd01.prod.outlook.com>
2016-12-15 8:26 ` [PATCH] HID: multitouch: enable the Surface 4 Type Cover Pro (JP) to report multitouch data benjamin.tissoires
2016-12-15 19:42 ` Jiri Kosina
[not found] ` <OSXPR01MB0791665ABC048023FE1E653EF29C0@OSXPR01MB0791.jpnprd01.prod.outlook.com>
2016-12-16 8:10 ` benjamin.tissoires [this message]
[not found] <OSXPR01MB07917D3BE92900CAB5CC44E9F29D0@OSXPR01MB0791.jpnprd01.prod.outlook.com>
2016-12-15 8:10 ` benjamin.tissoires
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=20161216081011.GF31881@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=alu.ula@outlook.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
/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).