From: Greg KH <gregkh@linuxfoundation.org>
To: "Stanisław Maciej Molsa" <stanislawmolsa@gmail.com>
Cc: peter.chen@kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: common: fix all alignment warnings in usb-otg-fsm.c
Date: Sun, 29 Mar 2026 08:20:39 +0200 [thread overview]
Message-ID: <2026032944-relic-attach-0786@gregkh> (raw)
In-Reply-To: <acgQzzfSTX-5foU-@stanislaw-QEMU-Virtual-Machine>
On Sat, Mar 28, 2026 at 05:33:03PM +0000, Stanisław Maciej Molsa wrote:
> Hi Peter,
>
> This is my first small contribution to the USB subsystem.
No need for this here.
>
> Fixed all "Alignment should match open parenthesis" warnings in
> usb-otg-fsm.c, as
> reported by checkpatch.pl
>
> Signed-off-by: Stanisław Maciej Molsa <stanislawmolsa@gmail.com>
> ---
> drivers/usb/common/usb-otg-fsm.c | 42 ++++++++++++++++----------------
> 1 file changed, 21 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/usb/common/usb-otg-fsm.c b/drivers/usb/common/usb-otg-fsm.c
> index e11803225775..5dcaa6c2057f 100644
> --- a/drivers/usb/common/usb-otg-fsm.c
> +++ b/drivers/usb/common/usb-otg-fsm.c
> @@ -32,7 +32,7 @@ static int otg_set_protocol(struct otg_fsm *fsm, int protocol)
>
> if (fsm->protocol != protocol) {
> VDBG("Changing role fsm->protocol= %d; new protocol= %d\n",
> - fsm->protocol, protocol);
> + fsm->protocol, protocol);
Please do not do coding style changes EXCEPT in subsystems that
specifically ask for them to be done in (like drivers/staging/),
otherwise there will be nothing but constant churn in the kernel tree.
thanks,
greg k-h
prev parent reply other threads:[~2026-03-29 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 17:33 [PATCH] usb: common: fix all alignment warnings in usb-otg-fsm.c Stanisław Maciej Molsa
2026-03-29 6:20 ` 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=2026032944-relic-attach-0786@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=stanislawmolsa@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