From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 8811/11214] arch/x86/pci/amd_bus.c:59:16: sparse: sparse: cast truncates bits from constant value (fcffffffff becomes ffffffff)
Date: Wed, 30 Aug 2023 20:02:01 +0800 [thread overview]
Message-ID: <202308301929.UtNM1sWc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 56585460cc2ec44fc5d66924f0a116f57080f0dc
commit: 7fe99c836ebd8e02d5cde4dae7d7559fa1ff2f01 [8811/11214] range.h: Move resource API and constant to respective files
config: i386-randconfig-061-20230830 (https://download.01.org/0day-ci/archive/20230830/202308301929.UtNM1sWc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230830/202308301929.UtNM1sWc-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308301929.UtNM1sWc-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/pci/amd_bus.c:59:16: sparse: sparse: cast truncates bits from constant value (fcffffffff becomes ffffffff)
vim +59 arch/x86/pci/amd_bus.c
53
54 static inline resource_size_t cap_resource(u64 val)
55 {
56 if (val > RESOURCE_SIZE_MAX)
57 return RESOURCE_SIZE_MAX;
58
> 59 return val;
60 }
61
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-30 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:02 kernel test robot [this message]
2023-08-31 16:28 ` Andy Shevchenko
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=202308301929.UtNM1sWc-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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