linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff LaBundy <jeff@labundy.com>
To: Albert Zhou <albert.zhou.50@gmail.com>
Cc: jikos@kernel.org, benjamin.tissoires@redhat.com,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] hid: add info to Kconfig
Date: Sun, 20 Nov 2022 12:48:19 -0600	[thread overview]
Message-ID: <Y3p2czhlHeg5Rf/l@nixie71> (raw)
In-Reply-To: <20221120033456.4332-1-albert.zhou.50@gmail.com>

Hi Albert,

On Sun, Nov 20, 2022 at 02:34:56PM +1100, Albert Zhou wrote:
> Nowadays many laptops use multitouch for their touchpads. This is now
> indicated in the help message for HID_MULTITOUCH in the Kconfig.
> 
> Signed-off-by: Albert Zhou <albert.zhou.50@gmail.com>
> ---
>  drivers/hid/Kconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
> index 185a077d59cd..86f65258a912 100644
> --- a/drivers/hid/Kconfig
> +++ b/drivers/hid/Kconfig
> @@ -697,7 +697,8 @@ config HID_MONTEREY
>  config HID_MULTITOUCH
>  	tristate "HID Multitouch panels"
>  	help
> -	  Generic support for HID multitouch panels.
> +	  Generic support for HID multitouch panels. Many newer laptops (like
> +	  the Dell XPS 13 9360) use multitouch for their touchpads.

This is just my opinion, but the intent is to describe what
the feature does, not make claims about what products might
happen to use it as of today.

Furthermore, "newer" is relative. This statement won't have
the same meaning years from now. I think the description is
fine as-is.

>  
>  	  Say Y here if you have one of the following devices:
>  	  - 3M PCT touch screens
> 
> base-commit: fe24a97cf2543e8832e7a2124802e5c32aac05aa
> -- 
> 2.34.1
> 

Kind regards,
Jeff LaBundy

  reply	other threads:[~2022-11-20 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20  3:34 [PATCH] hid: add info to Kconfig Albert Zhou
2022-11-20 18:48 ` Jeff LaBundy [this message]
2022-11-21  5:42   ` Albert Zhou

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=Y3p2czhlHeg5Rf/l@nixie71 \
    --to=jeff@labundy.com \
    --cc=albert.zhou.50@gmail.com \
    --cc=benjamin.tissoires@redhat.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).