linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Qin Jian <qinjian@cqplus1.com>, kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [clk:clk-sunplus 1/1] drivers/clk/clk-sp7021.c:316:8: warning: result of comparison of constant 18446744073709551615 with expression of type 'typeof (_Generic((_m), char: (unsigned char)0, unsigned char: (unsigned char)0, signed char: (unsigned char)0, unsigned short: (unsigne...
Date: Fri, 28 Apr 2023 18:13:34 -0700	[thread overview]
Message-ID: <e181f270191e30d99554496517bd321d.sboyd@kernel.org> (raw)
In-Reply-To: <20230324145056.GA428955@dev-arch.thelio-3990X>

Quoting Nathan Chancellor (2023-03-24 07:50:56)
> On Wed, Mar 22, 2023 at 04:48:43PM -0700, Stephen Boyd wrote:
> > Quoting Nathan Chancellor (2023-03-22 12:59:33)
> > 
> > > It looks like clang is
> > > complaining that mask is an unsigned int and it is being compared
> > > against ~0ull, which will always be false. This makes the warning go
> > > away for me, which is similar to commit cfd6fb45cfaf ("crypto: ccree -
> > > avoid out-of-range warnings from clang"), but I am not sure if that is
> > > correct or not.
> > 
> > Cool thanks. Can you send it as a proper patch?
> 
> Sure thing, I will do so when I am back online next week.
> 

Did you send the patch?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-29  1:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 11:17 [clk:clk-sunplus 1/1] drivers/clk/clk-sp7021.c:316:8: warning: result of comparison of constant 18446744073709551615 with expression of type 'typeof (_Generic((_m), char: (unsigned char)0, unsigned char: (unsigned char)0, signed char: (unsigned char)0, unsigned short: (unsigne kernel test robot
2023-03-22 17:39 ` Stephen Boyd
2023-03-22 19:59   ` Nathan Chancellor
2023-03-22 23:48     ` Stephen Boyd
2023-03-24 14:50       ` Nathan Chancellor
2023-04-29  1:13         ` Stephen Boyd [this message]
2023-05-01 16:28           ` Nathan Chancellor

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=e181f270191e30d99554496517bd321d.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=qinjian@cqplus1.com \
    /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).