From: walter harms <wharms@bfs.de>
To: Roberto Rodriguez Alkala <rralcala@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] stating: otus: fix compile warning and some style issues
Date: Sun, 08 Aug 2010 15:17:56 +0000 [thread overview]
Message-ID: <4C5ECAA4.9050606@bfs.de> (raw)
In-Reply-To: <1281225149.10826.5.camel@lenovo>
Roberto Rodriguez Alkala schrieb:
> In today linux-next I got a compile warning in staging/otus driver.
> This patch solves the issue and also improves the coding style.
>
> Signed-off-by: Roberto Rodriguez Alcala <rralcala@gmail.com>
> ---
> drivers/staging/otus/80211core/ratectrl.c | 26 +++++++++-----------------
> 1 files changed, 9 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/staging/otus/80211core/ratectrl.c b/drivers/staging/otus/80211core/ratectrl.c
> index a1abe2f..283b2b5 100644
> --- a/drivers/staging/otus/80211core/ratectrl.c
> +++ b/drivers/staging/otus/80211core/ratectrl.c
> @@ -422,23 +422,15 @@ u8_t zfRateCtrlRateDiff(struct zsRcCell* rcCell, u8_t retryRate)
> u16_t i;
>
> /* Find retryRate in operationRateSet[] */
> - for (i=0; i<rcCell->operationRateCount; i++)
> - {
> - if (retryRate = rcCell->operationRateSet[i])
> - {
> - if (i < rcCell->currentRateIndex)
> - {
> - return ((rcCell->currentRateIndex - i)+1)>>1;
> - }
> - else if (i = rcCell->currentRateIndex = 0)
> - {
> - return 1;
> - }
> - else
> - {
> - return 0;
> - }
> - }
> + for (i = 0; i < rcCell->operationRateCount; i++) {
> + if (retryRate = rcCell->operationRateSet[i]) {
> + if (i < rcCell->currentRateIndex)
> + return ((rcCell->currentRateIndex - i)+1)>>1;
> + else if (i = rcCell->currentRateIndex && i = 0)
> + return 1;
> + else
> + return 0;
> + }
> }
> /* TODO : retry rate not in operation rate set */
> zm_msg1_tx(ZM_LV_0, "Not in operation rate set:", retryRate);
mmh, it is a matter of taste but to improve readablity
i would make the special case i=0 first and let the loop
start with i=1. /* untested code below, assuming rcCell->currentRateIndex>=0 */
if ( retryRate = rcCell->operationRateSet[0] && rcCell->currentRateIndex= 0 )
return 1;
for (i = 1; i < rcCell->operationRateCount; i++) {
if (i < rcCell->currentRateIndex)
return ((rcCell->currentRateIndex - i)+1)>>1;
else
return 0;
}
just my 2 cents,
re,
wh
WARNING: multiple messages have this Message-ID (diff)
From: walter harms <wharms@bfs.de>
To: Roberto Rodriguez Alkala <rralcala@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] stating: otus: fix compile warning and some style issues
Date: Sun, 08 Aug 2010 17:17:56 +0200 [thread overview]
Message-ID: <4C5ECAA4.9050606@bfs.de> (raw)
In-Reply-To: <1281225149.10826.5.camel@lenovo>
Roberto Rodriguez Alkala schrieb:
> In today linux-next I got a compile warning in staging/otus driver.
> This patch solves the issue and also improves the coding style.
>
> Signed-off-by: Roberto Rodriguez Alcala <rralcala@gmail.com>
> ---
> drivers/staging/otus/80211core/ratectrl.c | 26 +++++++++-----------------
> 1 files changed, 9 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/staging/otus/80211core/ratectrl.c b/drivers/staging/otus/80211core/ratectrl.c
> index a1abe2f..283b2b5 100644
> --- a/drivers/staging/otus/80211core/ratectrl.c
> +++ b/drivers/staging/otus/80211core/ratectrl.c
> @@ -422,23 +422,15 @@ u8_t zfRateCtrlRateDiff(struct zsRcCell* rcCell, u8_t retryRate)
> u16_t i;
>
> /* Find retryRate in operationRateSet[] */
> - for (i=0; i<rcCell->operationRateCount; i++)
> - {
> - if (retryRate == rcCell->operationRateSet[i])
> - {
> - if (i < rcCell->currentRateIndex)
> - {
> - return ((rcCell->currentRateIndex - i)+1)>>1;
> - }
> - else if (i == rcCell->currentRateIndex == 0)
> - {
> - return 1;
> - }
> - else
> - {
> - return 0;
> - }
> - }
> + for (i = 0; i < rcCell->operationRateCount; i++) {
> + if (retryRate == rcCell->operationRateSet[i]) {
> + if (i < rcCell->currentRateIndex)
> + return ((rcCell->currentRateIndex - i)+1)>>1;
> + else if (i == rcCell->currentRateIndex && i == 0)
> + return 1;
> + else
> + return 0;
> + }
> }
> /* TODO : retry rate not in operation rate set */
> zm_msg1_tx(ZM_LV_0, "Not in operation rate set:", retryRate);
mmh, it is a matter of taste but to improve readablity
i would make the special case i=0 first and let the loop
start with i=1. /* untested code below, assuming rcCell->currentRateIndex>=0 */
if ( retryRate == rcCell->operationRateSet[0] && rcCell->currentRateIndex== 0 )
return 1;
for (i = 1; i < rcCell->operationRateCount; i++) {
if (i < rcCell->currentRateIndex)
return ((rcCell->currentRateIndex - i)+1)>>1;
else
return 0;
}
just my 2 cents,
re,
wh
next prev parent reply other threads:[~2010-08-08 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 23:52 [PATCH] stating: otus: fix compile warning and some style issues Roberto Rodriguez Alkala
2010-08-07 23:52 ` Roberto Rodriguez Alkala
2010-08-08 15:17 ` walter harms [this message]
2010-08-08 15:17 ` walter harms
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=4C5ECAA4.9050606@bfs.de \
--to=wharms@bfs.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rralcala@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 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.