From: Jes Sorensen <jes.sorensen@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>,
Janani Ravichandran <janani.rvchndrn@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: unisys: Modify boolean assignment
Date: Wed, 17 Feb 2016 12:59:49 -0500 [thread overview]
Message-ID: <56C4B515.3020301@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1602100954070.2486@hadrien>
On 02/10/16 03:54, Julia Lawall wrote:
>
>
> On Tue, 9 Feb 2016, Janani Ravichandran wrote:
>
>>
>>
>> On Wednesday, 10 February 2016 02:26:38 UTC-5, Julia Lawall wrote:
>> On Wed, 10 Feb 2016, Janani Ravichandran wrote:
>>
>> > Boolean variables should be assigned true/false rather than
>> 1/0.
>> > This patch makes such a correction.
>>
>> A change like this should be made consistently, so it is a
>> little
>> surprising to see only one such change. Is this the only place
>> where the
>> variable is initialized?
>>
>> Within this file, this is the only instance of initialization of the
>> variable where 1 is
>> used instead of true. All others use true/false. I sent this to resolve
>> that
>> inconsistency :)
>> If so, you could say that. if not, then you
>> could explain that all of the other initialization places
>> already have
>> boolean values, in some way or another.
>>
>> Do I send a v2 explaining this?
>
> I think it could be helpful.
You also need to CC the driver author, not just the outreachy list.
Jes
next prev parent reply other threads:[~2016-02-17 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 8:24 [PATCH] staging: unisys: Modify boolean assignment Janani Ravichandran
2016-02-10 7:26 ` [Outreachy kernel] " Julia Lawall
2016-02-10 7:45 ` Janani Ravichandran
2016-02-10 8:54 ` Julia Lawall
2016-02-17 17:59 ` Jes Sorensen [this message]
[not found] ` <20160217180323.GA23677@kroah.com>
2016-02-17 18:10 ` Jes Sorensen
2016-02-20 23:30 ` Greg KH
2016-02-22 13:07 ` Jes Sorensen
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=56C4B515.3020301@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=janani.rvchndrn@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.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.