From: kernel test robot <lkp@intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
gregkh@linuxfoundation.org, david.m.ertman@intel.com,
ira.weiny@intel.com, lee@kernel.org,
andriy.shevchenko@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Raag Jadav <raag.jadav@intel.com>
Subject: Re: [PATCH v1] mfd: core: Support auxiliary device
Date: Thu, 3 Apr 2025 23:11:12 +0800 [thread overview]
Message-ID: <202504032326.2F62UbVV-lkp@intel.com> (raw)
In-Reply-To: <20250403110053.1274521-1-raag.jadav@intel.com>
Hi Raag,
kernel test robot noticed the following build warnings:
[auto build test WARNING on driver-core/driver-core-testing]
[also build test WARNING on driver-core/driver-core-next driver-core/driver-core-linus lee-mfd/for-mfd-next lee-leds/for-leds-next linus/master v6.14 next-20250403]
[cannot apply to lee-mfd/for-mfd-fixes]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Raag-Jadav/mfd-core-Support-auxiliary-device/20250403-190322
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20250403110053.1274521-1-raag.jadav%40intel.com
patch subject: [PATCH v1] mfd: core: Support auxiliary device
config: arm-randconfig-002-20250403 (https://download.01.org/0day-ci/archive/20250403/202504032326.2F62UbVV-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250403/202504032326.2F62UbVV-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/202504032326.2F62UbVV-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/peci/cpu.c:4:
include/linux/auxiliary_bus.h: In function 'auxiliary_device_uninit':
include/linux/auxiliary_bus.h:246:3: error: implicit declaration of function 'kfree'; did you mean 'ida_free'? [-Werror=implicit-function-declaration]
kfree(auxdev->resource);
^~~~~
ida_free
In file included from drivers/peci/cpu.c:8:
include/linux/slab.h: At top level:
>> include/linux/slab.h:472:6: warning: conflicting types for 'kfree'
void kfree(const void *objp);
^~~~~
In file included from drivers/peci/cpu.c:4:
include/linux/auxiliary_bus.h:246:3: note: previous implicit declaration of 'kfree' was here
kfree(auxdev->resource);
^~~~~
cc1: some warnings being treated as errors
vim +/kfree +472 include/linux/slab.h
7bd230a26648ac Suren Baghdasaryan 2024-03-21 471
72d67229f522e3 Kees Cook 2021-11-05 @472 void kfree(const void *objp);
72d67229f522e3 Kees Cook 2021-11-05 473 void kfree_sensitive(const void *objp);
72d67229f522e3 Kees Cook 2021-11-05 474 size_t __ksize(const void *objp);
05a940656e1eb2 Kees Cook 2022-09-23 475
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-03 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 11:00 [PATCH v1] mfd: core: Support auxiliary device Raag Jadav
2025-04-03 14:02 ` Greg KH
2025-04-03 14:16 ` Andy Shevchenko
2025-04-03 14:19 ` Andy Shevchenko
2025-04-03 14:23 ` Greg KH
2025-04-03 14:26 ` Andy Shevchenko
2025-04-03 14:31 ` Raag Jadav
2025-04-04 11:36 ` Raag Jadav
2025-04-04 12:29 ` Andy Shevchenko
2025-04-04 12:35 ` Raag Jadav
2025-04-04 13:00 ` Andy Shevchenko
2025-04-04 13:39 ` Raag Jadav
2025-04-04 13:56 ` Andy Shevchenko
2025-04-04 14:47 ` Raag Jadav
2025-04-03 15:11 ` kernel test robot [this message]
2025-04-03 15:11 ` kernel test robot
2025-04-03 21:39 ` kernel test robot
2025-04-04 15:35 ` Lee Jones
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=202504032326.2F62UbVV-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raag.jadav@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.