[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZugDzBHmTCdMagWR@smile.fi.intel.com>
Date: Mon, 16 Sep 2024 13:09:16 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: kernel test robot <lkp@...el.com>
Cc: Parker Newman <parker@...est.io>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, Arnd Bergmann <arnd@...db.de>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
oe-kbuild-all@...ts.linux.dev,
Parker Newman <pnewman@...necttech.com>
Subject: Re: [PATCH v1 4/6] serial: 8250_exar: Replace custom EEPROM read
with eeprom_93cx6
On Sat, Sep 14, 2024 at 09:26:27PM +0800, kernel test robot wrote:
> Hi Parker,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on 5ed771f174726ae879945d4f148a9005ac909cb7]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Parker-Newman/misc-eeprom-eeprom_93cx6-Add-quirk-for-extra-read-clock-cycle/20240913-230345
> base: 5ed771f174726ae879945d4f148a9005ac909cb7
> patch link: https://lore.kernel.org/r/78dead78311ea619e0be99cc32ee0df1610a480d.1726237379.git.pnewman%40connecttech.com
> patch subject: [PATCH v1 4/6] serial: 8250_exar: Replace custom EEPROM read with eeprom_93cx6
> config: x86_64-randconfig-122-20240914 (https://download.01.org/0day-ci/archive/20240914/202409142138.yCOHBlL1-lkp@intel.com/config)
> compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409142138.yCOHBlL1-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202409142138.yCOHBlL1-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> drivers/tty/serial/8250/8250_exar.c:739:13: sparse: sparse: restricted __le32 degrades to integer
Yes, and this should gone if Parker follows my suggestion on how to handle this.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists