From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/kasan/kasan_init: use true and false for boolean values
Date: Mon, 6 Aug 2018 06:39:02 -0500 [thread overview]
Message-ID: <0413df4d-262d-fee8-f1a3-99ccf1d3a441@embeddedor.com> (raw)
In-Reply-To: <CACT4Y+arVJ4qt54LzKKoyh9+NKA+fjyCShKi82NanbovhK_mmQ@mail.gmail.com>
Hi Dmitry,
On 08/06/2018 04:04 AM, Dmitry Vyukov wrote:
> On Sun, Aug 5, 2018 at 12:08 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.
>>
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>
> Hi Gustavo,
>
> I don't see this code in upstream tree. Is it against some other tree? Which?
>
Yep. It's against linux-next.
Should I use [PATCH next] in the subject next time?
Thanks
--
Gustavo
> Thanks
>
>> ---
>> mm/kasan/kasan_init.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/kasan/kasan_init.c b/mm/kasan/kasan_init.c
>> index 7a2a2f1..c742dc5 100644
>> --- a/mm/kasan/kasan_init.c
>> +++ b/mm/kasan/kasan_init.c
>> @@ -42,7 +42,7 @@ static inline bool kasan_p4d_table(pgd_t pgd)
>> #else
>> static inline bool kasan_p4d_table(pgd_t pgd)
>> {
>> - return 0;
>> + return false;
>> }
>> #endif
>> #if CONFIG_PGTABLE_LEVELS > 3
>> @@ -54,7 +54,7 @@ static inline bool kasan_pud_table(p4d_t p4d)
>> #else
>> static inline bool kasan_pud_table(p4d_t p4d)
>> {
>> - return 0;
>> + return false;
>> }
>> #endif
>> #if CONFIG_PGTABLE_LEVELS > 2
>> @@ -66,7 +66,7 @@ static inline bool kasan_pmd_table(pud_t pud)
>> #else
>> static inline bool kasan_pmd_table(pud_t pud)
>> {
>> - return 0;
>> + return false;
>> }
>> #endif
>> pte_t kasan_zero_pte[PTRS_PER_PTE] __page_aligned_bss;
>> --
>> 2.7.4
next prev parent reply other threads:[~2018-08-06 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 22:08 Gustavo A. R. Silva
2018-08-06 9:04 ` Dmitry Vyukov
2018-08-06 11:39 ` Gustavo A. R. Silva [this message]
2018-08-06 12:05 ` Dmitry Vyukov
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=0413df4d-262d-fee8-f1a3-99ccf1d3a441@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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