From: walter harms <wharms@bfs.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Firo Yang <firogm@gmail.com>,
neilb@suse.de, linux-raid@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] md: fix a build warning
Date: Wed, 10 Jun 2015 20:04:18 +0200 [thread overview]
Message-ID: <55787C22.2060809@bfs.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1506101935390.5463@hadrien>
Am 10.06.2015 19:36, schrieb Julia Lawall:
>
>
> On Wed, 10 Jun 2015, walter harms wrote:
>
>>
>>
>> Am 10.06.2015 17:20, schrieb Firo Yang:
>>> Warning like this:
>>>
>>> drivers/md/md.c: In function ‘update_array_info’:
>>> drivers/md/md.c:6394:26: warning: logical not is only applied
>>> to the left hand side of comparison [-Wlogical-not-parentheses]
>>> !mddev->persistent != info->not_persistent||
>>>
>>> I fix it by enclosing !mddev->persistent with parentheses
>>>
>>> By the way, I also fixed a line over 80 characters warning outputed
>>> by ./scripts/checkpatch.pl
>>>
>>> Signed-off-by: Firo Yang <firogm@gmail.com>
>>> ---
>>> drivers/md/md.c | 5 +++--
>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>>> index dd85be9..b420d82 100644
>>> --- a/drivers/md/md.c
>>> +++ b/drivers/md/md.c
>>> @@ -6391,9 +6391,10 @@ static int update_array_info(struct mddev *mddev, mdu_array_info_t *info)
>>> mddev->ctime != info->ctime ||
>>> mddev->level != info->level ||
>>> /* mddev->layout != info->layout || */
>>> - !mddev->persistent != info->not_persistent||
>>> + (!mddev->persistent) != info->not_persistent ||
>>
>>
>> this looks odd,
>> would it be possible the check for == instead (and drop the !) ?
>> and it someone care for readability: It would be helpful to
>> make some more ifs here.
>
> The original issue looks like a false positive. If all of the other cases
> have no parentheses on the left and use !=, isn't it better to leave the
> code as is?
>
i do not think so, the name indicate persistent/not_persistent devices.
Maybe both parties can agree what should be stored, ppl are bad
at those not_not things and that is an unnecessary trouble spot.
re,
wh
> julia
>
>>
>> re,
>> wh
>>
>>> mddev->chunk_sectors != info->chunk_size >> 9 ||
>>> - /* ignore bottom 8 bits of state, and allow SB_BITMAP_PRESENT to change */
>>> + /* ignore bottom 8 bits of state, and allow SB_BITMAP_PRESENT
>>> + to change */
>>> ((state^info->state) & 0xfffffe00)
>>> )
>>> return -EINVAL;
>> --
>> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-10 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 15:20 [PATCH] md: fix a build warning Firo Yang
2015-06-10 16:07 ` Dan Carpenter
2015-06-10 17:32 ` walter harms
2015-06-10 17:36 ` Julia Lawall
2015-06-10 18:04 ` walter harms [this message]
2015-06-10 20:38 ` Neil Brown
2015-06-10 20:34 ` Neil Brown
2015-06-11 11:48 ` Dan Carpenter
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=55787C22.2060809@bfs.de \
--to=wharms@bfs.de \
--cc=firogm@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).