All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: mateng <ayowoe@163.com>, dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	mateng <mateng@yulong.com>
Subject: Re: [PATCH] touchscreen/goodix.c:unify format
Date: Mon, 24 May 2021 10:48:09 +0200	[thread overview]
Message-ID: <3bd72f4181488c0066eee1674afaf26fea1d3a0c.camel@hadess.net> (raw)
In-Reply-To: <20210524024619.1227-1-ayowoe@163.com>

On Mon, 2021-05-24 at 10:46 +0800, mateng wrote:
> From: mateng <mateng@yulong.com>
> 
> unify format

This doesn't "unify the format", it adds commas where none are needed.

NAK

> 
> Signed-off-by: mateng <mateng@yulong.com>
> ---
>  drivers/input/touchscreen/goodix.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/goodix.c
> b/drivers/input/touchscreen/goodix.c
> index c682b02..ab12065 100644
> --- a/drivers/input/touchscreen/goodix.c
> +++ b/drivers/input/touchscreen/goodix.c
> @@ -210,7 +210,7 @@ static int goodix_check_cfg_16(struct
> goodix_ts_data *ts,
>                 .matches = {
>                         DMI_MATCH(DMI_SYS_VENDOR, "WinBook"),
>                         DMI_MATCH(DMI_PRODUCT_NAME, "TW100")
> -               }
> +               },
>         },
>         {
>                 .ident = "WinBook TW700",
> @@ -230,7 +230,7 @@ static int goodix_check_cfg_16(struct
> goodix_ts_data *ts,
>                 /* YB1-X91L/F and YB1-X90L/F */
>                 .matches = {
>                         DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9")
> -               }
> +               },
>         },
>  #endif
>         {}



      reply	other threads:[~2021-05-24  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  2:46 [PATCH] touchscreen/goodix.c:unify format mateng
2021-05-24  8:48 ` Bastien Nocera [this message]

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=3bd72f4181488c0066eee1674afaf26fea1d3a0c.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=ayowoe@163.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mateng@yulong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.