From: Markus Elfring <Markus.Elfring@web.de>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 3/3] ath6kl: Reduce scopes for two variables in ath6kl_sdio_power_on()
Date: Mon, 23 Sep 2024 19:00:05 +0200 [thread overview]
Message-ID: <45f6c8a7-4021-483a-aa81-a836cd3fbcd8@web.de> (raw)
In-Reply-To: <80b820cd-9255-473e-8e4a-3e7d8612d876@quicinc.com>
>> Adjust the definitions for the local variables "func" and "ret"
>> so that the corresponding setting will be performed a bit later.
…
>> +++ b/drivers/net/wireless/ath/ath6kl/sdio.c
>> @@ -503,17 +503,15 @@ static void ath6kl_sdio_irq_handler(struct sdio_func *func)
>> static int ath6kl_sdio_power_on(struct ath6kl *ar)
>> {
>> struct ath6kl_sdio *ar_sdio = ath6kl_sdio_priv(ar);
>> - struct sdio_func *func = ar_sdio->func;
>> - int ret = 0;
>>
>> if (!ar_sdio->is_disabled)
>> return 0;
>>
>> ath6kl_dbg(ATH6KL_DBG_BOOT, "sdio power on\n");
>> -
>> + struct sdio_func *func = ar_sdio->func;
>> sdio_claim_host(func);
>>
>> - ret = sdio_enable_func(func);
>> + int ret = sdio_enable_func(func);
>> sdio_release_host(func);
>> if (ret) {
>> ath6kl_err("Unable to enable sdio func: %d)\n", ret);
>> --
>> 2.46.0
>
> NAK
>
> no maintainer wants to spend time on patches like this which bring no real
> value to code that is not actively being maintained, and which violates the
> established understanding that, except under certain recently established
> criteria, declarations and code should not be interleaved.
…
Would you find other software design options more acceptable for further
collateral evolution?
1. Additional compound statements (by using extra curly brackets)
2. Moving a bit of source code into an additional function implementation
Regards,
Markus
next prev parent reply other threads:[~2024-09-23 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 12:00 [PATCH 0/3] ath6kl: Adjustments for ath6kl_sdio_power_on() Markus Elfring
2024-09-21 12:02 ` [PATCH 1/3] ath6kl: Use sdio_release_host(func) call only once in ath6kl_sdio_power_on() Markus Elfring
2024-09-21 12:04 ` [PATCH 2/3] ath6kl: Omit a label " Markus Elfring
2024-09-21 12:06 ` [PATCH 3/3] ath6kl: Reduce scopes for two variables " Markus Elfring
2024-09-23 16:41 ` Jeff Johnson
2024-09-23 17:00 ` Markus Elfring [this message]
2024-09-23 18:21 ` Jeff Johnson
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=45f6c8a7-4021-483a-aa81-a836cd3fbcd8@web.de \
--to=markus.elfring@web.de \
--cc=julia.lawall@inria.fr \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=quic_jjohnson@quicinc.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