From: hch@lst.de
To: kbuild-all@lists.01.org
Subject: Re: [asahilinux:bits/050-nvme 6/9] drivers/nvme/host/apple.c:291:19: sparse: sparse: incorrect type in assignment (different base types)
Date: Mon, 27 Jun 2022 03:04:32 +0000 [thread overview]
Message-ID: <20220625095115.GA23965@lst.de> (raw)
In-Reply-To: <e874d1f9-912e-487e-bd8c-e227067c00ca@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
On Sat, Jun 25, 2022 at 11:46:55AM +0200, Sven Peter wrote:
> 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.
Perfect, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Sven Peter <sven@svenpeter.dev>
Cc: "hch@lst.de" <hch@lst.de>, kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Hector Martin <marcan@marcan.st>, Arnd Bergmann <arnd@arndb.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)
Date: Sat, 25 Jun 2022 11:51:15 +0200 [thread overview]
Message-ID: <20220625095115.GA23965@lst.de> (raw)
In-Reply-To: <e874d1f9-912e-487e-bd8c-e227067c00ca@www.fastmail.com>
On Sat, Jun 25, 2022 at 11:46:55AM +0200, Sven Peter wrote:
> 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.
Perfect, thanks!
next prev parent reply other threads:[~2022-06-27 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 7:55 [asahilinux:bits/050-nvme 6/9] drivers/nvme/host/apple.c:291:19: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2022-06-25 7:59 ` Christoph Hellwig
2022-06-25 7:59 ` Christoph Hellwig
2022-06-25 9:46 ` Sven Peter
2022-06-27 3:04 ` Sven Peter
2022-06-25 9:51 ` hch [this message]
2022-06-27 3:04 ` hch
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=20220625095115.GA23965@lst.de \
--to=hch@lst.de \
--cc=kbuild-all@lists.01.org \
/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.