linux-kernel - Re: [asahilinux:bits/050-nvme 6/9] drivers/nvme/host/apple.c:291:19: sparse: sparse: incorrect type in assignment (different base types)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <e874d1f9-912e-487e-bd8c-e227067c00ca@www.fastmail.com>
Date:   Sat, 25 Jun 2022 11:46:55 +0200
From:   "Sven Peter" <sven@...npeter.dev>
To:     "hch@....de" <hch@....de>, "kernel test robot" <lkp@...el.com>
Cc:     kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
        "Hector Martin" <marcan@...can.st>, "Arnd Bergmann" <arnd@...db.de>
Subject: Re: [asahilinux:bits/050-nvme 6/9] drivers/nvme/host/apple.c:291:19: sparse:
 sparse: incorrect type in assignment (different base types)

On Sat, Jun 25, 2022, at 09:59, Christoph Hellwig wrote:
> Sven, can you send a patch to use the proper __le types?  We really
> prefer the nvme code to no have any sparse warnings.

Arnd already fixed this with 7ad7ab90368 after the commits hit the soc tree
(and before I even had a chance to look at it).
This mail just came from our downstream tree that's still stuck at 5.18.


Sven