linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Joe Perches <joe@perches.com>,
	David Laight <David.Laight@ACULAB.COM>,
	'Andy Shevchenko' <andy.shevchenko@gmail.com>
Cc: "Lee, Chun-Yi" <jlee@suse.com>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: acer-wmi: use true and false for boolean values
Date: Mon, 6 Aug 2018 12:24:26 -0500	[thread overview]
Message-ID: <bae13020-ca76-ca57-c14c-93e5f64c295d@embeddedor.com> (raw)
In-Reply-To: <fa7980ee38e6cbb31883e1b942fa1e1d6f0e72b0.camel@perches.com>



On 08/06/2018 11:42 AM, Joe Perches wrote:
> On Mon, 2018-08-06 at 16:41 +0000, David Laight wrote:
>> From: Andy Shevchenko
>>> Sent: 05 August 2018 11:26
>>>
>>> On Sun, Aug 5, 2018 at 3:18 AM, Gustavo A. R. Silva
>>> <gustavo@embeddedor.com> wrote:
>>>> Return statements in functions returning bool should use true or false
>>>> instead of an integer value.
>>>>
>>>> This code was detected with the help of Coccinelle.
>>>>  static bool has_cap(u32 cap)
>>>>  {
>>>>         if ((interface->capability & cap) != 0)
>>>> -               return 1;
>>>> +               return true;
>>>>
>>>> -       return 0;
>>>> +       return false;
>>>>  }
>>>
>>> this entire function can be oneliner:
>>>
>>> return !!(...);
>>
>> Why the !! ?? Just:
>> 	return (interface->capability & cap) != 0;
> 
> Because the return is bool you don't need the !! either.
> The compiler does that.
> 

Hi all,

I'll send v2 with the suggested improvements.

Thanks for your feedback.
--
Gustavo

  reply	other threads:[~2018-08-06 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05  0:18 [PATCH] platform/x86: acer-wmi: use true and false for boolean values Gustavo A. R. Silva
2018-08-05 10:26 ` Andy Shevchenko
2018-08-06 16:41   ` David Laight
2018-08-06 16:42     ` Joe Perches
2018-08-06 17:24       ` Gustavo A. R. Silva [this message]
2018-08-06 19:06       ` Andy Shevchenko

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=bae13020-ca76-ca57-c14c-93e5f64c295d@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=jlee@suse.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).