From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [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: Thu, 31 Aug 2023 19:28:40 +0300 [thread overview]
Message-ID: <ZPC/uPEXEwQimtWw@smile.fi.intel.com> (raw)
In-Reply-To: <202308301929.UtNM1sWc-lkp@intel.com>
On Wed, Aug 30, 2023 at 08:02:01PM +0800, kernel test robot wrote:
...
> commit: 7fe99c836ebd8e02d5cde4dae7d7559fa1ff2f01
range.h: Move resource API and constant to respective files
No, this is false positive. The warning was before that
include/linux/range.h:40:16: warning: cast truncates bits from constant value (fcffffffff becomes ffffffff)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-08-31 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:02 [linux-next:master 8811/11214] arch/x86/pci/amd_bus.c:59:16: sparse: sparse: cast truncates bits from constant value (fcffffffff becomes ffffffff) kernel test robot
2023-08-31 16:28 ` Andy Shevchenko [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=ZPC/uPEXEwQimtWw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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 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.