public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nelson, Shannon" <shannon.nelson@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, kernel test robot <lkp@intel.com>
Cc: Brett Creeley <brett.creeley@amd.com>,
	oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Leon Romanovsky <leonro@nvidia.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: drivers/fwctl/pds/main.c:113:65: sparse: sparse: restricted __le32 degrades to integer
Date: Wed, 2 Apr 2025 08:57:04 -0700	[thread overview]
Message-ID: <9f7ba2e9-58d8-499e-a67b-c79a647eafc7@amd.com> (raw)
In-Reply-To: <20250402122833.GB327284@ziepe.ca>

On 4/2/2025 5:28 AM, Jason Gunthorpe wrote:
> 
> On Wed, Apr 02, 2025 at 02:46:38AM +0800, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   08733088b566b58283f0f12fb73f5db6a9a9de30
>> commit: 92c66ee829b99a860a90f62ef16df3e42f92edac pds_fwctl: add rpc and query support
>> date:   11 days ago
>> config: loongarch-randconfig-r111-20250401 (https://download.01.org/0day-ci/archive/20250402/202504020246.Dfbhxoo9-lkp@intel.com/config)
>> compiler: loongarch64-linux-gcc (GCC) 14.2.0
>> reproduce: (https://download.01.org/0day-ci/archive/20250402/202504020246.Dfbhxoo9-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/202504020246.Dfbhxoo9-lkp@intel.com/
> 
> Shannon, can you send a patch to fix all the sparse errors?
> 
> Thanks

Yes, I have one mostly ready, should get it sent out later today.
sln


> 
>> sparse warnings: (new ones prefixed by >>)
>>>> drivers/fwctl/pds/main.c:113:65: sparse: sparse: restricted __le32 degrades to integer
>>>> drivers/fwctl/pds/main.c:202:50: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] endpoint @@     got restricted __le32 [usertype] id @@
>>     drivers/fwctl/pds/main.c:202:50: sparse:     expected unsigned int [usertype] endpoint
>>     drivers/fwctl/pds/main.c:202:50: sparse:     got restricted __le32 [usertype] id
>>     drivers/fwctl/pds/main.c:250:29: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:288:39: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:294:40: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:300:41: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:329:44: sparse: sparse: restricted __le32 degrades to integer
>>>> drivers/fwctl/pds/main.c:330:21: sparse: sparse: cast to restricted __le32
>>     drivers/fwctl/pds/main.c:330:21: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:330:21: sparse: sparse: restricted __le32 degrades to integer
>>>> drivers/fwctl/pds/main.c:330:21: sparse: sparse: cast to restricted __le32
>>     drivers/fwctl/pds/main.c:330:21: sparse: sparse: restricted __le32 degrades to integer
>>     drivers/fwctl/pds/main.c:330:21: sparse: sparse: restricted __le32 degrades to integer
>>>> drivers/fwctl/pds/main.c:405:56: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le16 [usertype] flags @@     got int @@
>>     drivers/fwctl/pds/main.c:405:56: sparse:     expected restricted __le16 [usertype] flags
>>     drivers/fwctl/pds/main.c:405:56: sparse:     got int


      reply	other threads:[~2025-04-02 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 18:46 drivers/fwctl/pds/main.c:113:65: sparse: sparse: restricted __le32 degrades to integer kernel test robot
2025-04-02 12:28 ` Jason Gunthorpe
2025-04-02 15:57   ` Nelson, Shannon [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=9f7ba2e9-58d8-499e-a67b-c79a647eafc7@amd.com \
    --to=shannon.nelson@amd.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=brett.creeley@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox