From: Alexander Aring <aahringo@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
David Teigland <teigland@redhat.com>,
cluster-devel <cluster-devel@redhat.com>
Subject: Re: fs/dlm/midcomms.c:913:22: sparse: sparse: restricted __le32 degrades to integer
Date: Sat, 22 Jan 2022 13:28:20 -0500 [thread overview]
Message-ID: <CAK-6q+h_hb94J3DSXPk=E44kCxiwZ+BE3kMJe09iShRzMb=vzQ@mail.gmail.com> (raw)
In-Reply-To: <202201221028.YKA8kSdm-lkp@intel.com>
Hi,
On Fri, Jan 21, 2022 at 9:45 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 9b57f458985742bd1c585f4c7f36d04634ce1143
> commit: 658bd576f95ed597e519cdadf1c86ac87c17aea5 fs: dlm: move version conversion to compile time
> date: 3 months ago
> config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20220122/202201221028.YKA8kSdm-lkp@intel.com/config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce:
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=658bd576f95ed597e519cdadf1c86ac87c17aea5
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 658bd576f95ed597e519cdadf1c86ac87c17aea5
> # save the config file to linux build tree
> mkdir build_dir
> make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
I have it on my list but it isn't easy to make sparse happy here...
this is the second time the robot reported this issue. Is there a way
to turn the robot off in that case?
Maybe some human who reads that knows the answer?
Thanks.
- Alex
next prev parent reply other threads:[~2022-01-22 18:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 2:45 fs/dlm/midcomms.c:913:22: sparse: sparse: restricted __le32 degrades to integer kernel test robot
2022-01-22 18:28 ` Alexander Aring [this message]
2022-01-22 19:18 ` Randy Dunlap
2022-01-23 18:41 ` Alexander Aring
2022-01-24 12:45 ` Dan Carpenter
2022-01-24 17:21 ` Alexander Aring
2022-01-24 17:36 ` Alexander Aring
2022-01-24 17:41 ` Alexander Aring
2022-01-24 20:14 ` Paul E. McKenney
2022-01-24 21:36 ` Alexander Aring
2022-01-24 22:06 ` Paul E. McKenney
2022-01-25 22:35 ` Alexander Aring
2022-01-26 14:39 ` Alexander Aring
2022-02-14 5:13 ` Al Viro
2022-02-14 12:47 ` Alexander Aring
2022-01-24 22:45 kernel test robot
2022-01-26 2:28 kernel test robot
2022-02-07 18:21 kernel test robot
2022-02-08 22:19 kernel test robot
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='CAK-6q+h_hb94J3DSXPk=E44kCxiwZ+BE3kMJe09iShRzMb=vzQ@mail.gmail.com' \
--to=aahringo@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=teigland@redhat.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).