From: Raag Jadav <raag.jadav@intel.com>
To: kernel test robot <lkp@intel.com>, andriy.shevchenko@linux.intel.com
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
dmitry.torokhov@gmail.com, lgirdwood@gmail.com,
broonie@kernel.org, sre@kernel.org, jic23@kernel.org,
przemyslaw.kitszel@intel.com, oe-kbuild-all@lists.linux.dev,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-sound@vger.kernel.org,
linux-pm@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 01/20] driver core: Split devres APIs to device/devres.h
Date: Thu, 6 Feb 2025 08:13:12 +0200 [thread overview]
Message-ID: <Z6RS-A2FFjYuPoyn@black.fi.intel.com> (raw)
In-Reply-To: <202502060025.XJwUub6I-lkp@intel.com>
On Thu, Feb 06, 2025 at 12:27:03AM +0800, kernel test robot wrote:
> Hi Raag,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on 2014c95afecee3e76ca4a56956a936e23283f05b]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Raag-Jadav/driver-core-Split-devres-APIs-to-device-devres-h/20250203-161554
> base: 2014c95afecee3e76ca4a56956a936e23283f05b
> patch link: https://lore.kernel.org/r/20250203080902.1864382-2-raag.jadav%40intel.com
> patch subject: [PATCH v3 01/20] driver core: Split devres APIs to device/devres.h
> config: um-randconfig-r112-20250205 (https://download.01.org/0day-ci/archive/20250206/202502060025.XJwUub6I-lkp@intel.com/config)
> compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 355d0b186f178668b103068537e517f3d52ad639)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250206/202502060025.XJwUub6I-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@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202502060025.XJwUub6I-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> drivers/net/pcs/pcs-xpcs-plat.c: note: in included file (through include/linux/device.h):
> >> include/linux/device/devres.h:106:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
> include/linux/device/devres.h:106:23: sparse: expected void [noderef] __iomem *
> include/linux/device/devres.h:106:23: sparse: got void *
>
> vim +106 include/linux/device/devres.h
>
> 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?
Raag
next prev parent reply other threads:[~2025-02-06 6:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 8:08 [PATCH v3 00/20] Split devres APIs to device/devres.h and introduce devm_kmemdup_array() Raag Jadav
2025-02-03 8:08 ` [PATCH v3 01/20] driver core: Split devres APIs to device/devres.h Raag Jadav
2025-02-05 16:27 ` kernel test robot
2025-02-06 6:13 ` Raag Jadav [this message]
2025-02-06 15:12 ` Andy Shevchenko
2025-02-06 15:14 ` Andy Shevchenko
2025-02-06 18:11 ` Raag Jadav
2025-02-06 18:56 ` Andy Shevchenko
2025-02-03 8:08 ` [PATCH v3 02/20] iio: imu: st_lsm9ds0: Replace device.h with what is needed Raag Jadav
2025-02-03 11:19 ` Jonathan Cameron
2025-02-03 8:08 ` [PATCH v3 03/20] devres: Introduce devm_kmemdup_array() Raag Jadav
2025-02-03 8:08 ` [PATCH v3 04/20] pinctrl: intel: copy communities using devm_kmemdup_array() Raag Jadav
2025-02-03 8:08 ` [PATCH v3 05/20] pinctrl: baytrail: " Raag Jadav
2025-02-06 18:45 ` Linus Walleij
2025-02-03 8:08 ` [PATCH v3 06/20] pinctrl: cherryview: use devm_kmemdup_array() Raag Jadav
2025-02-06 18:46 ` Linus Walleij
2025-02-03 8:08 ` [PATCH v3 07/20] pinctrl: tangier: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 08/20] pinctrl: pxa2xx: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 09/20] input: sparse-keymap: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 10/20] input: ipaq-micro-keys: " Raag Jadav
2025-02-06 18:46 ` Linus Walleij
2025-02-03 8:08 ` [PATCH v3 11/20] regulator: devres: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 12/20] regulator: cros-ec: " Raag Jadav
2025-02-03 9:51 ` Andy Shevchenko
2025-02-03 10:40 ` Raag Jadav
2025-02-03 11:23 ` Andy Shevchenko
2025-02-03 8:08 ` [PATCH v3 13/20] power: supply: sc27xx: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 14/20] iio: adc: xilinx-xadc-core: " Raag Jadav
2025-02-03 9:54 ` Andy Shevchenko
2025-02-03 10:42 ` Raag Jadav
2025-02-03 11:14 ` Jonathan Cameron
2025-02-03 11:25 ` Andy Shevchenko
2025-02-03 11:24 ` Andy Shevchenko
2025-02-03 8:08 ` [PATCH v3 15/20] ASoC: Intel: avs: " Raag Jadav
2025-02-03 8:08 ` [PATCH v3 16/20] ASoC: hdac_hdmi: " Raag Jadav
2025-02-03 9:52 ` Andy Shevchenko
2025-02-03 8:08 ` [PATCH v3 17/20] ASoC: tlv320dac33: " Raag Jadav
2025-02-03 9:52 ` Andy Shevchenko
2025-02-03 8:09 ` [PATCH v3 18/20] ASoC: uda1380: " Raag Jadav
2025-02-03 9:57 ` Andy Shevchenko
2025-02-03 8:09 ` [PATCH v3 19/20] ASoC: meson: axg-tdm-interface: " Raag Jadav
2025-02-03 8:09 ` [PATCH v3 20/20] ASoC: uniphier: " Raag Jadav
2025-02-03 9:53 ` Andy Shevchenko
2025-02-03 9:48 ` [PATCH v3 00/20] Split devres APIs to device/devres.h and introduce devm_kmemdup_array() Andy Shevchenko
2025-02-03 10:34 ` Raag Jadav
2025-02-03 11:29 ` Andy Shevchenko
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=Z6RS-A2FFjYuPoyn@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=przemyslaw.kitszel@intel.com \
--cc=rafael@kernel.org \
--cc=sre@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).