[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6TRveCRK7LFwSNV@smile.fi.intel.com>
Date: Thu, 6 Feb 2025 17:14:05 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Raag Jadav <raag.jadav@...el.com>
Cc: kernel test robot <lkp@...el.com>, gregkh@...uxfoundation.org,
rafael@...nel.org, linus.walleij@...aro.org,
mika.westerberg@...ux.intel.com, dmitry.torokhov@...il.com,
lgirdwood@...il.com, broonie@...nel.org, sre@...nel.org,
jic23@...nel.org, przemyslaw.kitszel@...el.com,
oe-kbuild-all@...ts.linux.dev, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
linux-sound@...r.kernel.org, linux-pm@...r.kernel.org,
linux-iio@...r.kernel.org
Subject: Re: [PATCH v3 01/20] driver core: Split devres APIs to
device/devres.h
On Thu, Feb 06, 2025 at 05:12:49PM +0200, Andy Shevchenko wrote:
> On Thu, Feb 06, 2025 at 08:13:12AM +0200, Raag Jadav wrote:
> > On Thu, Feb 06, 2025 at 12:27:03AM +0800, kernel test robot wrote:
...
> > > 102
> > > 103 static inline
> > > 104 void __iomem *devm_ioremap_resource(struct device *dev, const struct resource *res)
> > > 105 {
> > > > 106 return ERR_PTR(-EINVAL);
> > > 107 }
> > > 108
> >
> > Andy, are we expecting this?
>
> Oh, no, it's sparse error, but easy to fix. Need to have
>
> return IOMEM_ERR_PTR(-EINVAL);
But isn't it the original issue? I mean that it was already before this series.
If so, perhaps you can fix all sparse errors like this in the devres* code.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists