public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Josh Law <hlcj1234567@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Josh Law <objecting@objecting.org>
Subject: Re: [PATCH v2 1/4] Input: elo - fix style issues
Date: Sun, 1 Mar 2026 16:25:12 -0800	[thread overview]
Message-ID: <aaTYvqdymKquoVWJ@google.com> (raw)
In-Reply-To: <20260228195258.2468296-1-objecting@objecting.org>

Hi Josh,

On Sat, Feb 28, 2026 at 07:52:58PM +0000, Josh Law wrote:
> Fix array constness and spacing issues reported by checkpatch.
> 
> Signed-off-by: Josh Law <objecting@objecting.org>

Why the difference between From: and Signed-off-by?

> ---
>  drivers/input/touchscreen/elo.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/elo.c b/drivers/input/touchscreen/elo.c
> index 434b9b47e964..40ae132cde21 100644
> --- a/drivers/input/touchscreen/elo.c
> +++ b/drivers/input/touchscreen/elo.c
> @@ -257,7 +257,7 @@ static int elo_command_10(struct elo *elo, unsigned char *packet)
>  
>  static int elo_setup_10(struct elo *elo)
>  {
> -	static const char *elo_types[] = { "Accu", "Dura", "Intelli", "Carroll" };
> +	static const char * const elo_types[] = { "Accu", "Dura", "Intelli", "Carroll" };
>  	struct input_dev *dev = elo->dev;
>  	unsigned char packet[ELO10_PACKET_LEN] = { ELO10_ID_CMD };
>  
> @@ -273,7 +273,7 @@ static int elo_setup_10(struct elo *elo)
>  
>  	dev_info(&elo->serio->dev,
>  		 "%sTouch touchscreen, fw: %02x.%02x, features: 0x%02x, controller: 0x%02x\n",
> -		 elo_types[(packet[1] -'0') & 0x03],
> +		 elo_types[(packet[1] - '0') & 0x03],
>  		 packet[5], packet[4], packet[3], packet[7]);
>  
>  	return 0;

Thanks.

-- 
Dmitry

  reply	other threads:[~2026-03-02  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 19:52 [PATCH v2 1/4] Input: elo - fix style issues Josh Law
2026-03-02  0:25 ` Dmitry Torokhov [this message]
2026-03-02  7:13   ` Josh Law

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=aaTYvqdymKquoVWJ@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=hlcj1234567@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=objecting@objecting.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