From: kernel test robot <[email protected]>
To: Alexandre Ghiti <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
[email protected], [email protected],
Palmer Dabbelt <[email protected]>
Subject: [PATCH] riscv: fix boolconv.cocci warnings
Date: Wed, 19 Jan 2022 11:38:36 +0800 [thread overview]
Message-ID: <20220119033836.GA4900@68f8e94b87ce> (raw)
In-Reply-To: <[email protected]>
From: kernel test robot <[email protected]>
arch/riscv/mm/init.c:48:11-16: WARNING: conversion to bool not needed here
Remove unneeded conversion to bool
Semantic patch information:
Relational and logical operators evaluate to bool,
explicit conversion is overly verbose and unneeded.
Generated by: scripts/coccinelle/misc/boolconv.cocci
CC: Alexandre Ghiti <[email protected]>
Reported-by: kernel test robot <[email protected]>
Signed-off-by: kernel test robot <[email protected]>
---
tree: https://github.com/ammarfaizi2/linux-block palmer/linux/riscv-sv48
head: d87f3297c62644624bcb8efcb519a2e28d684b45
commit: dee563c628683ce1fab7d0267ad96fc7d8503965 [7/9] riscv: Implement sv48 support
:::::: branch date: 8 hours ago
:::::: commit date: 8 hours ago
init.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -44,8 +44,7 @@ u64 satp_mode = SATP_MODE_32;
#endif
EXPORT_SYMBOL(satp_mode);
-bool pgtable_l4_enabled = IS_ENABLED(CONFIG_64BIT) && !IS_ENABLED(CONFIG_XIP_KERNEL) ?
- true : false;
+bool pgtable_l4_enabled = IS_ENABLED(CONFIG_64BIT) && !IS_ENABLED(CONFIG_XIP_KERNEL);
EXPORT_SYMBOL(pgtable_l4_enabled);
phys_addr_t phys_ram_base __ro_after_init;
--
GWML mailing list
[email protected]
https://gwml.gnuweeb.org/listinfo/gwml
prev parent reply other threads:[~2022-01-19 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 3:41 [ammarfaizi2-block:palmer/linux/riscv-sv48 7/9] arch/riscv/mm/init.c:48:11-16: WARNING: conversion to bool not needed here kernel test robot
2022-01-19 3:38 ` kernel test robot [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=20220119033836.GA4900@68f8e94b87ce \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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