From: Chen Gang <chengang@emindsoft.com.cn>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: akpm@linux-foundation.org, dhowells@redhat.com,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH] include/linux/list_bl.h: Use bool instead of int for boolean functions
Date: Thu, 28 Jan 2016 23:24:03 +0800 [thread overview]
Message-ID: <56AA3293.4010601@emindsoft.com.cn> (raw)
In-Reply-To: <20160128072236.GA5067@osiris>
On 1/28/16 15:22, Heiko Carstens wrote:
> On Mon, Jan 25, 2016 at 04:58:18AM +0800, chengang@emindsoft.com.cn wrote:
>> From: Chen Gang <chengang@emindsoft.com.cn>
>>
>> hlist_bl_unhashed() and hlist_bl_empty() are all boolean functions, so
>> return bool instead of int.
>>
>> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
>> ---
>> include/linux/list_bl.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/list_bl.h b/include/linux/list_bl.h
>> index ee7229a..cb48330 100644
>> --- a/include/linux/list_bl.h
>> +++ b/include/linux/list_bl.h
>> @@ -48,7 +48,7 @@ static inline void INIT_HLIST_BL_NODE(struct hlist_bl_node *h)
>>
>> #define hlist_bl_entry(ptr, type, member) container_of(ptr,type,member)
>>
>> -static inline int hlist_bl_unhashed(const struct hlist_bl_node *h)
>> +static inline bool hlist_bl_unhashed(const struct hlist_bl_node *h)
>> {
>> return !h->pprev;
>> }
>> @@ -68,7 +68,7 @@ static inline void hlist_bl_set_first(struct hlist_bl_head *h,
>> h->first = (struct hlist_bl_node *)((unsigned long)n | LIST_BL_LOCKMASK);
>> }
>>
>> -static inline int hlist_bl_empty(const struct hlist_bl_head *h)
>> +static inline bool hlist_bl_empty(const struct hlist_bl_head *h)
>> {
>> return !((unsigned long)READ_ONCE(h->first) & ~LIST_BL_LOCKMASK);
>
> Sorry for my ignorance, but what's the point of doing conversions like
> this? It has zero impact on code generation.
>
For me, in our case, the 2 functions really generate boolean value, and
they are really used as boolean functions, so returning boolean value
will let the code a little simpler and a little clearer.
Thanks.
--
Chen Gang (陈刚)
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2016-01-28 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 20:58 [PATCH] include/linux/list_bl.h: Use bool instead of int for boolean functions chengang
2016-01-28 7:22 ` Heiko Carstens
2016-01-28 15:24 ` Chen Gang [this message]
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=56AA3293.4010601@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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.