From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: drivers/pci/proc.c:150:17: sparse: sparse: restricted __le16 degrades to integer
Date: Tue, 29 Mar 2022 08:56:24 +0200 [thread overview]
Message-ID: <20220329065624.GB20158@lst.de> (raw)
In-Reply-To: <202203281004.InhLOFxn-lkp@intel.com>
Looks like new uaccess code doesn't handle sparse __bitwise annotations.
next prev parent reply other threads:[~2022-03-29 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 3:04 drivers/pci/proc.c:150:17: sparse: sparse: restricted __le16 degrades to integer kernel test robot
2022-03-29 6:56 ` Christoph Hellwig [this message]
2022-03-31 8:43 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 7:42 kernel test robot
2022-06-04 7:54 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=20220329065624.GB20158@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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