From: Randy Dunlap <rdunlap@infradead.org>
To: Matthias Yee <mgyee9@gmail.com>, gregkh@linuxfoundation.org
Cc: dan.carpenter@linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: fix open parentheses alignment
Date: Tue, 9 Jan 2024 23:30:17 -0800 [thread overview]
Message-ID: <e3941caa-7546-415f-be7b-b955cf13aa8b@infradead.org> (raw)
In-Reply-To: <20240110072304.2226-1-mgyee9@gmail.com>
Greg, Dan,
On 1/9/24 23:23, Matthias Yee wrote:
> Adjusted whitespace to fix checkpatch warning Alignment Should Match
> Open Parenthesis.
>
> Signed-off-by: Matthias Yee <mgyee9@gmail.com>
> ---
> Changes in v3
> -fixed line wrapping for commit message
> ---
> drivers/staging/vt6655/card.c | 74 +++++++++++++++++------------------
> 1 file changed, 37 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c
> index 36183f2a64c1..688c870d89bc 100644
> --- a/drivers/staging/vt6655/card.c
> +++ b/drivers/staging/vt6655/card.c
> @@ -81,9 +81,9 @@ static void vt6655_mac_set_bb_type(void __iomem *iobase, u32 mask)
> * Return Value: none
> */
> static void calculate_ofdmr_parameter(unsigned char rate,
> - u8 bb_type,
> - unsigned char *tx_rate,
> - unsigned char *rsv_time)
> + u8 bb_type,
> + unsigned char *tx_rate,
> + unsigned char *rsv_time)
> {
> switch (rate) {
> case RATE_6M:
Is there any chance that checkpatch is wrong about this warning?
I much prefer the alignment as it was before this patch: following lines
are aligned with the first parameter after the '('.
--
#Randy
next prev parent reply other threads:[~2024-01-10 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:23 Matthias Yee
2024-01-10 7:26 ` Dan Carpenter
2024-01-10 7:30 ` Randy Dunlap [this message]
2024-01-10 7:51 ` Dan Carpenter
2024-01-10 7:56 ` Randy Dunlap
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=e3941caa-7546-415f-be7b-b955cf13aa8b@infradead.org \
--to=rdunlap@infradead.org \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgyee9@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
all inboxes | Powered by JetHome®