From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Matthias Yee <mgyee9@gmail.com>,
gregkh@linuxfoundation.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:56:30 -0800 [thread overview]
Message-ID: <9fdcb306-862f-4ad5-a52f-cd70fd21cf05@infradead.org> (raw)
In-Reply-To: <f22e751e-863a-46a9-8dd6-0ac55f1ad9c8@moroto.mountain>
On 1/9/24 23:51, Dan Carpenter wrote:
> On Tue, Jan 09, 2024 at 11:30:17PM -0800, Randy Dunlap wrote:
>>> 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 '('.
>>
>
> It just looks weird in the diff because of the + character at the front
> and how the tabs work out. It looks ok in the code.
Oops, sorry, you are correct. Thanks!
--
#Randy
prev parent reply other threads:[~2024-01-10 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:23 [PATCH v3] staging: vt6655: fix open parentheses alignment Matthias Yee
2024-01-10 7:26 ` Dan Carpenter
2024-01-10 7:30 ` Randy Dunlap
2024-01-10 7:51 ` Dan Carpenter
2024-01-10 7:56 ` Randy Dunlap [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=9fdcb306-862f-4ad5-a52f-cd70fd21cf05@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