public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <bentiss@kernel.org>
To: aravindanilraj0702@gmail.com
Cc: jikos@kernel.org, linux-input@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: cherry: Fix switch case formatting
Date: Thu, 26 Mar 2026 17:35:06 +0100	[thread overview]
Message-ID: <acVfxor2SwDrufkw@beelink> (raw)
In-Reply-To: <20260325161328.260110-1-aravindanilraj0702@gmail.com>

On Mar 25 2026, aravindanilraj0702@gmail.com wrote:
> From: Aravind Anilraj <aravindanilraj0702@gmail.com>
> 
> Fix checkpatch warnings by splitting single-line case
> statements into multiple lines.
> 
> No functional changes.
> 
> Signed-off-by: Aravind Anilraj <aravindanilraj0702@gmail.com>
> ---
>  drivers/hid/hid-cherry.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/hid/hid-cherry.c b/drivers/hid/hid-cherry.c
> index a504632febfc..828a3cc67512 100644
> --- a/drivers/hid/hid-cherry.c
> +++ b/drivers/hid/hid-cherry.c
> @@ -43,9 +43,15 @@ static int ch_input_mapping(struct hid_device *hdev, struct hid_input *hi,
>  		return 0;
>  
>  	switch (usage->hid & HID_USAGE) {
> -	case 0x301: ch_map_key_clear(KEY_PROG1);	break;
> -	case 0x302: ch_map_key_clear(KEY_PROG2);	break;
> -	case 0x303: ch_map_key_clear(KEY_PROG3);	break;
> +	case 0x301:
> +		ch_map_key_clear(KEY_PROG1);
> +		break;
> +	case 0x302:
> +		ch_map_key_clear(KEY_PROG2);
> +		break;
> +	case 0x303:
> +		ch_map_key_clear(KEY_PROG3);
> +		break;

Nack: please don't run checkpatch on existing and already merged code.

This comment is valid for all the other similar patches you sent today.

There are many reasons to refuse such a patch, but mostly it's just
pointless and makes looking into the history harder.

If you fix something in the code, then yes, you can also make formatting
fixes, but formatting for just fomratting is going to be rejected in all
subsystems you attempt to contribute to.

Cheers,
Benjamin

>  	default:
>  		return 0;
>  	}
> -- 
> 2.47.3
> 
> 

      reply	other threads:[~2026-03-26 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 16:13 [PATCH] HID: cherry: Fix switch case formatting aravindanilraj0702
2026-03-26 16:35 ` Benjamin Tissoires [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=acVfxor2SwDrufkw@beelink \
    --to=bentiss@kernel.org \
    --cc=aravindanilraj0702@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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