[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YZ0cKQiMS/E8z7Jh@smile.fi.intel.com>
Date: Tue, 23 Nov 2021 18:51:53 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Jon Hunter <jonathanh@...dia.com>
Cc: Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v1 1/2] spi: deduplicate spi_match_id() in
__spi_register_driver()
On Tue, Nov 23, 2021 at 03:22:38PM +0000, Jon Hunter wrote:
> On 19/11/2021 17:37, Andy Shevchenko wrote:
> Following this change I am seeing the following warnings again although most
> of these have now been fixed ...
>
> WARNING KERN SPI driver mtd_dataflash has no spi_device_id for atmel,at45
> WARNING KERN SPI driver mtd_dataflash has no spi_device_id for
> atmel,dataflash
> WARNING KERN SPI driver spi-nor has no spi_device_id for jedec,spi-nor
> WARNING KERN SPI driver mmc_spi has no spi_device_id for mmc-spi-slot
> WARNING KERN SPI driver cros-ec-spi has no spi_device_id for
> google,cros-ec-spi
> I have not looked any further yet, but this appears to cause the SPI ID
> match to fail.
Looking into the code it should be harmless warning. I.o.w. it shouldn't
prevent driver registration. In any case I'm about to send a fix, thanks
for the report!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists