From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-ide@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ata: pata_ali: remove redundant return statement
Date: Thu, 13 Jan 2022 00:11:43 +0000 [thread overview]
Message-ID: <a049118e-888b-991b-8df8-640c828b4e08@gmail.com> (raw)
In-Reply-To: <2d9b4f08-967e-6040-a954-e7bfa7e4dce1@opensource.wdc.com>
On 12/01/2022 23:52, Damien Le Moal wrote:
> On 1/13/22 08:47, Colin Ian King wrote:
>> A return statement is unnecessarily complicated, currently value
>> in variable mask is bitwise-masked and the variable is being
>> updated and then returned. Just updating the mask is all that is
>> required as the following statement is a return.
>>
>> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
>> ---
>> drivers/ata/pata_ali.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/pata_ali.c b/drivers/ata/pata_ali.c
>> index ab28a6707b94..1b90cda27246 100644
>> --- a/drivers/ata/pata_ali.c
>> +++ b/drivers/ata/pata_ali.c
>> @@ -123,7 +123,7 @@ static unsigned long ali_20_filter(struct ata_device *adev, unsigned long mask)
>> mask &= ~(ATA_MASK_MWDMA | ATA_MASK_UDMA);
>> ata_id_c_string(adev->id, model_num, ATA_ID_PROD, sizeof(model_num));
>> if (strstr(model_num, "WDC"))
>> - return mask &= ~ATA_MASK_UDMA;
>
> Yeah, not to mention that is really ugly as the return should really
> have been:
>
> return mask & ~ATA_MASK_UDMA;
Yep, I did think of that as the original intention, but two return
statements one after the other was equally as ugly. It was a 50/50
choice of what was perceived as the better fix :-)
>
>> + mask &= ~ATA_MASK_UDMA;
>> return mask;
>> }
>>
>
> Will queue this up.
>
Thank you.
prev parent reply other threads:[~2022-01-13 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 23:47 Colin Ian King
2022-01-12 23:52 ` Damien Le Moal
2022-01-13 0:11 ` Colin King (gmail) [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=a049118e-888b-991b-8df8-640c828b4e08@gmail.com \
--to=colin.i.king@gmail.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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®