From: Greg KH <gregkh@linuxfoundation.org>
To: "Darshan R." <rathod.darshan.0896@gmail.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: storage: Checkpatch fix done and Clean up coding style
Date: Fri, 25 Jul 2025 15:58:31 +0200 [thread overview]
Message-ID: <2025072526-guru-reacquire-408d@gregkh> (raw)
In-Reply-To: <20250725135533.8410-1-rathod.darshan.0896@gmail.com>
On Fri, Jul 25, 2025 at 01:55:33PM +0000, Darshan R. wrote:
> The shuttle_usbat.c driver has several coding style inconsistencies that deviate from the Linux kernel standard.
> This makes the code harder to read and maintain.
>
> This patch is a pure cleanup effort to address these style issues.
> The changes include:
>
> - Adding proper spacing around operators (=, *, +, !=, etc.).
> - Adjusting pointer declarations to the standard type *var style.
> - Fixing spacing in pointer casts, e.g., (struct usbat_info *).
> - Removing the redundant = 0 initializer for the static transferred
> variable, as it's guaranteed to be zero-initialized.
> - Tidying up miscellaneous whitespace and removing extra blank lines.
>
> These changes were guided by checkpatch.pl.
> No functional changes have been made.
>
> Signed-off-by: Darshan R. <rathod.darshan.0896@gmail.com>
> ---
> drivers/usb/storage/shuttle_usbat.c | 252 +++++++++++++---------------
> 1 file changed, 120 insertions(+), 132 deletions(-)
Please do not run checkpatch.pl on existing subsystems and old kernel
code and then send a huge patch to "fix them all!". That's not going to
work well for many kernel subsystems as they do not welcome the constant
churn that would cause.
If you are interested in doing this type of work, do so in the
drivers/staging/ subsystem, which welcomes it.
thanks,
greg k-h
prev parent reply other threads:[~2025-07-25 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 13:55 [PATCH] usb: storage: Checkpatch fix done and Clean up coding style Darshan R.
2025-07-25 13:58 ` Greg KH [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=2025072526-guru-reacquire-408d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rathod.darshan.0896@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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).