From: kernel test robot <lkp@intel.com>
To: trix@redhat.com, hao.wu@intel.com, mdf@kernel.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-fpga@vger.kernel.org, Tom Rix <trix@redhat.com>
Subject: Re: [PATCH] fpga: region: handle compat_id as an uuid
Date: Tue, 27 Jul 2021 07:35:12 +0800 [thread overview]
Message-ID: <202107270712.a50O2Grb-lkp@intel.com> (raw)
In-Reply-To: <20210726202650.4074614-1-trix@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.14-rc3 next-20210726]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/trix-redhat-com/fpga-region-handle-compat_id-as-an-uuid/20210727-042850
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ff1176468d368232b684f75e82563369208bc371
config: x86_64-randconfig-s032-20210726 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/fc6e727a3f214d2b60561c3accc1f054982e2281
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review trix-redhat-com/fpga-region-handle-compat_id-as-an-uuid/20210727-042850
git checkout fc6e727a3f214d2b60561c3accc1f054982e2281
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/fpga/dfl-fme-mgr.c:278:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] id_l @@ got restricted __be64 [usertype] @@
drivers/fpga/dfl-fme-mgr.c:278:18: sparse: expected unsigned long long [usertype] id_l
drivers/fpga/dfl-fme-mgr.c:278:18: sparse: got restricted __be64 [usertype]
>> drivers/fpga/dfl-fme-mgr.c:279:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] id_h @@ got restricted __be64 [usertype] @@
drivers/fpga/dfl-fme-mgr.c:279:18: sparse: expected unsigned long long [usertype] id_h
drivers/fpga/dfl-fme-mgr.c:279:18: sparse: got restricted __be64 [usertype]
vim +278 drivers/fpga/dfl-fme-mgr.c
274
275 static void fme_mgr_get_compat_id(void __iomem *fme_pr,
276 union fpga_compat_id *id)
277 {
> 278 id->id_l = cpu_to_be64(readq(fme_pr + FME_PR_INTFC_ID_L));
> 279 id->id_h = cpu_to_be64(readq(fme_pr + FME_PR_INTFC_ID_H));
280 }
281
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31853 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] fpga: region: handle compat_id as an uuid
Date: Tue, 27 Jul 2021 07:35:12 +0800 [thread overview]
Message-ID: <202107270712.a50O2Grb-lkp@intel.com> (raw)
In-Reply-To: <20210726202650.4074614-1-trix@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.14-rc3 next-20210726]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/trix-redhat-com/fpga-region-handle-compat_id-as-an-uuid/20210727-042850
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ff1176468d368232b684f75e82563369208bc371
config: x86_64-randconfig-s032-20210726 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/fc6e727a3f214d2b60561c3accc1f054982e2281
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review trix-redhat-com/fpga-region-handle-compat_id-as-an-uuid/20210727-042850
git checkout fc6e727a3f214d2b60561c3accc1f054982e2281
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/fpga/dfl-fme-mgr.c:278:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] id_l @@ got restricted __be64 [usertype] @@
drivers/fpga/dfl-fme-mgr.c:278:18: sparse: expected unsigned long long [usertype] id_l
drivers/fpga/dfl-fme-mgr.c:278:18: sparse: got restricted __be64 [usertype]
>> drivers/fpga/dfl-fme-mgr.c:279:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] id_h @@ got restricted __be64 [usertype] @@
drivers/fpga/dfl-fme-mgr.c:279:18: sparse: expected unsigned long long [usertype] id_h
drivers/fpga/dfl-fme-mgr.c:279:18: sparse: got restricted __be64 [usertype]
vim +278 drivers/fpga/dfl-fme-mgr.c
274
275 static void fme_mgr_get_compat_id(void __iomem *fme_pr,
276 union fpga_compat_id *id)
277 {
> 278 id->id_l = cpu_to_be64(readq(fme_pr + FME_PR_INTFC_ID_L));
> 279 id->id_h = cpu_to_be64(readq(fme_pr + FME_PR_INTFC_ID_H));
280 }
281
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31853 bytes --]
next prev parent reply other threads:[~2021-07-26 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 20:26 [PATCH] fpga: region: handle compat_id as an uuid trix
2021-07-26 22:12 ` Russ Weight
2021-07-27 0:16 ` Tom Rix
2021-07-28 1:36 ` Wu, Hao
2021-07-29 18:51 ` Moritz Fischer
2021-07-29 19:16 ` Tom Rix
2021-07-30 1:48 ` Xu Yilun
2021-07-30 12:07 ` Tom Rix
2021-08-03 3:32 ` Xu Yilun
2021-08-03 12:21 ` Tom Rix
2021-08-04 1:44 ` Xu Yilun
2021-08-04 13:21 ` Tom Rix
2021-08-06 1:42 ` Xu Yilun
2021-07-26 23:35 ` kernel test robot [this message]
2021-07-26 23:35 ` 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=202107270712.a50O2Grb-lkp@intel.com \
--to=lkp@intel.com \
--cc=hao.wu@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.