From: Yury Norov <yury.norov@gmail.com>
To: Alexander Lobakin <alexandr.lobakin@intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, platform-driver-x86@vger.kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] x86/olpc: fix 'logical not is only applied to the left hand side'
Date: Fri, 15 Jul 2022 08:45:23 -0700 [thread overview]
Message-ID: <YtGLkx1E8ZifiUQo@yury-laptop> (raw)
In-Reply-To: <20220715151536.67401-1-alexandr.lobakin@intel.com>
On Fri, Jul 15, 2022 at 05:15:36PM +0200, Alexander Lobakin wrote:
> The bitops compile-time optimization series revealed one more
> problem in olpc-xo1-sci.c:send_ebook_state(), resulted in GCC
> warnings:
>
> arch/x86/platform/olpc/olpc-xo1-sci.c: In function 'send_ebook_state':
> arch/x86/platform/olpc/olpc-xo1-sci.c:83:63: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses]
> 83 | if (!!test_bit(SW_TABLET_MODE, ebook_switch_idev->sw) == state)
> | ^~
> arch/x86/platform/olpc/olpc-xo1-sci.c:83:13: note: add parentheses around left hand side expression to silence this warning
>
> Despite this code working as intended, this redundant double
> negation of boolean value, together with comparing to `char`
> with no explicit conversion to bool, makes compilers think
> the author made some unintentional logical mistakes here.
> Make it the other way around and negate the char instead
> to silence the warnings.
>
> Fixes: d2aa37411b8e ("x86/olpc/xo1/sci: Produce wakeup events for buttons and switches")
> Cc: stable@vger.kernel.org # 3.5+
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Reported-by: kernel test robot <lkp@intel.com>
> Reviewed-and-tested-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Alexander Lobakin <alexandr.lobakin@intel.com>
Applied, thanks!
> ---
> arch/x86/platform/olpc/olpc-xo1-sci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/platform/olpc/olpc-xo1-sci.c b/arch/x86/platform/olpc/olpc-xo1-sci.c
> index f03a6883dcc6..89f25af4b3c3 100644
> --- a/arch/x86/platform/olpc/olpc-xo1-sci.c
> +++ b/arch/x86/platform/olpc/olpc-xo1-sci.c
> @@ -80,7 +80,7 @@ static void send_ebook_state(void)
> return;
> }
>
> - if (!!test_bit(SW_TABLET_MODE, ebook_switch_idev->sw) == state)
> + if (test_bit(SW_TABLET_MODE, ebook_switch_idev->sw) == !!state)
> return; /* Nothing new to report. */
>
> input_report_switch(ebook_switch_idev, SW_TABLET_MODE, state);
> --
> 2.36.1
prev parent reply other threads:[~2022-07-15 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 15:15 Alexander Lobakin
2022-07-15 15:45 ` Yury Norov [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=YtGLkx1E8ZifiUQo@yury-laptop \
--to=yury.norov@gmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®