From: Dan Carpenter <error27@gmail.com>
To: JunHyeok Seo <starlights2283@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: align AES function parameters with open parenthesis
Date: Wed, 9 Sep 2026 17:57:03 +0300 [thread overview]
Message-ID: <aqFzv98OAFRzeD_j@stanley.mountain> (raw)
In-Reply-To: <20260905072033.54813-1-starlights2283@gmail.com>
On Sat, Sep 05, 2026 at 04:20:33PM +0900, JunHyeok Seo wrote:
> Align the continuation lines of the aes_cipher()
> parameter lists with their opening parenthesis,
> and replace the stray tab between the uint type
> and the hdrlen argument with a single space.
This paragraph should be wrapped at 72 characters.
>
> This addresses the "Alignment should match open parenthesis" check
> reported by checkpatch.pl --strict.
>
> No functional change.
>
> Signed-off-by: JunHyeok Seo <starlights2283@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_security.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_security.c b/drivers/staging/rtl8723bs/core/rtw_security.c
> index 2217cffac5f2..3de102a27517 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_security.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_security.c
> @@ -765,8 +765,8 @@ static void construct_ctr_preload(u8 *ctr_preload,
> ctr_preload[15] = (unsigned char)(c % 256);
> }
>
> -static signed int aes_cipher(u8 *key, uint hdrlen,
> - u8 *pframe, uint plen)
> +static signed int aes_cipher(u8 *key, uint hdrlen,
> + u8 *pframe, uint plen)
Unless it's specified by the protocol spec, then "signed int" is
nonsense. Plus the caller doesn't check so it might as well be
void.
regards,
dan carpenter
prev parent reply other threads:[~2026-09-09 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 7:20 JunHyeok Seo
2026-09-09 14:57 ` Dan Carpenter [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=aqFzv98OAFRzeD_j@stanley.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=starlights2283@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®