From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Akiyoshi Kurita <weibu@redadmin.org>
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: fix function definition style in hal_com_phycfg.c
Date: Fri, 12 Sep 2025 15:53:08 +0200 [thread overview]
Message-ID: <2025091245-efficient-preaching-9e0e@gregkh> (raw)
In-Reply-To: <20250908172925.58312-1-weibu@redadmin.org>
On Tue, Sep 09, 2025 at 02:29:25AM +0900, Akiyoshi Kurita wrote:
> Several function definitions in this file did not follow the kernel
> coding style, spreading arguments across multiple lines.
>
> As requested by Dan Carpenter, fix all instances to place the function
> parameters and the closing parenthesis on the same line as the function
> name, improving readability and conforming to style guidelines.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> .../staging/rtl8723bs/hal/hal_com_phycfg.c | 33 ++++---------------
> 1 file changed, 6 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c b/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
> index 75ed731bbb14..fa987a797b16 100644
> --- a/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
> +++ b/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
> @@ -61,8 +61,6 @@ phy_SetTxPowerByRateBase(struct adapter *Adapter, u8 RfPath,
>
> static void
> phy_StoreTxPowerByRateBase(struct adapter *padapter)
> -{
> - u8 path, base;
>
> for (path = RF_PATH_A; path <= RF_PATH_B; ++path) {
> base = PHY_GetTxPowerByRate(padapter, path, MGN_11M);
This patch doesn't apply, nor does it even look like it can build? Did
you test-build the result?
thanks,
greg k-h
prev parent reply other threads:[~2025-09-12 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 17:29 [PATCH v2] staging: rtl8723bs: fix function definition style in hal_com_phycfg.c Akiyoshi Kurita
2025-09-12 13:53 ` Greg Kroah-Hartman [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=2025091245-efficient-preaching-9e0e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=weibu@redadmin.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.