mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: mickflemm@gmail.com, mcgrof@kernel.org, kvalo@kernel.org,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] ath5k: fix WARNING opportunity for swap.
Date: Wed, 9 Aug 2023 12:40:44 +0200	[thread overview]
Message-ID: <83f73eda-829d-2657-9f10-8ccf78522e5a@kernel.org> (raw)
In-Reply-To: <20230808194258.ocxnmqwzqlr6jpe4@mmaatuq-HP-Laptop-15-dy2xxx>

On 08. 08. 23, 21:42, Mahmoud Matook wrote:
> On 08/08, Jiri Slaby wrote:
> 
>> On 07. 08. 23, 22:10, Mahmoud Maatuq wrote:
>>> coccinielle reported the following:
>>> ./drivers/net/wireless/ath/ath5k/phy.c:1573:25-26: WARNING opportunity for swap()
>>
>>
>> OK, once again:
>> https://lore.kernel.org/all/0c3acbd4-6ab2-5cc5-6293-54e30093cce2@kernel.org/
> 
> 
> I had a look at the commit history, to see why the original developer
> didn't use sort() function, and name the array variable sort but found
> nothing.
> I have some doubts that he might did that intentionally, so not to call
> sort() function for such small array

It happens once in 10 s and in a work. No worries about that.

> and avoid the cost of context switching.

What context switching?

>>> diff --git a/drivers/net/wireless/ath/ath5k/phy.c b/drivers/net/wireless/ath/ath5k/phy.c
>>> index 5797ef9c73d7..f87eb684f223 100644
>>> --- a/drivers/net/wireless/ath/ath5k/phy.c
>>> +++ b/drivers/net/wireless/ath/ath5k/phy.c
>>> @@ -1562,16 +1562,13 @@ static s16
>>>    ath5k_hw_get_median_noise_floor(struct ath5k_hw *ah)
>>>    {
>>>    	s16 sort[ATH5K_NF_CAL_HIST_MAX];
>>> -	s16 tmp;
>>>    	int i, j;
>>>    	memcpy(sort, ah->ah_nfcal_hist.nfval, sizeof(sort));
>>>    	for (i = 0; i < ATH5K_NF_CAL_HIST_MAX - 1; i++) {
>>>    		for (j = 1; j < ATH5K_NF_CAL_HIST_MAX - i; j++) {
>>>    			if (sort[j] > sort[j - 1]) {
>>> -				tmp = sort[j];
>>> -				sort[j] = sort[j - 1];
>>> -				sort[j - 1] = tmp;
>>> +				swap(sort[j], sort[j - 1]);
>>>    			}
>>>    		}
>>>    	}
>>
>> -- 
>> js
>> suse labs

-- 
js
suse labs


  reply	other threads:[~2023-08-09 10:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 20:10 Mahmoud Maatuq
2023-08-08  6:02 ` Jiri Slaby
2023-08-08 19:42   ` Mahmoud Matook
2023-08-09 10:40     ` Jiri Slaby [this message]
2023-08-12  4:57     ` Mahmoud Matook

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=83f73eda-829d-2657-9f10-8ccf78522e5a@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mickflemm@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®