linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	pali@kernel.org, dmitry.torokhov@gmail.com, rydberg@bitmath.org,
	colin.king@canonical.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: input: mouse: Change postive to positive in the file alps.c
Date: Mon, 22 Feb 2021 00:07:40 -0800	[thread overview]
Message-ID: <97932a41-0d3b-adaa-3b08-35c6e81763ff@infradead.org> (raw)
In-Reply-To: <20210222075439.32201-1-unixbhaskar@gmail.com>

On 2/21/21 11:54 PM, Bhaskar Chowdhury wrote:
> 
> s/postive/positive/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  drivers/input/mouse/alps.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
> index b067bfd2699c..4a6b33bbe7ea 100644
> --- a/drivers/input/mouse/alps.c
> +++ b/drivers/input/mouse/alps.c
> @@ -986,7 +986,7 @@ static void alps_get_finger_coordinate_v7(struct input_mt_pos *mt,
>  	case V7_PACKET_ID_TWO:
>  		mt[1].x &= ~0x000F;
>  		mt[1].y |= 0x000F;
> -		/* Detect false-postive touches where x & y report max value */
> +		/* Detect false-positive touches where x & y report max value */
>  		if (mt[1].y == 0x7ff && mt[1].x == 0xff0) {
>  			mt[1].x = 0;
>  			/* y gets set to 0 at the end of this function */
> --


-- 
~Randy


  reply	other threads:[~2021-02-22  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  7:54 [PATCH] drivers: input: mouse: Change postive to positive in the file alps.c Bhaskar Chowdhury
2021-02-22  8:07 ` Randy Dunlap [this message]
2021-02-22  9:09   ` Pali Rohár

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=97932a41-0d3b-adaa-3b08-35c6e81763ff@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=colin.king@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=rydberg@bitmath.org \
    --cc=unixbhaskar@gmail.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).