Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 25 Jun 2022 11:51:15 +0200
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)
Message-ID: <20220625095115.GA23965@lst.de>
References: <202206251551.PTd0wn6d-lkp@intel.com> <20220625075950.GA22592@lst.de> <e874d1f9-912e-487e-bd8c-e227067c00ca@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e874d1f9-912e-487e-bd8c-e227067c00ca@www.fastmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Precedence: bulk

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!