From: kernel test robot <lkp@intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, "Michael Walle" <michael@walle.cc>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Frank Rowand" <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Robert Marko" <robert.marko@sartura.hr>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Luka Perkov" <luka.perkov@sartura.hr>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Daniel Golle" <daniel@makrotopia.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v11 5/7] nvmem: core: Rework layouts to become regular devices
Date: Thu, 5 Oct 2023 16:24:36 +0800 [thread overview]
Message-ID: <202310051638.C8Yz2WIY-lkp@intel.com> (raw)
In-Reply-To: <20231004222236.411248-6-miquel.raynal@bootlin.com>
Hi Miquel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on char-misc/char-misc-testing char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.6-rc4 next-20231005]
[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/Miquel-Raynal/of-device-Export-of_device_make_bus_id/20231005-062417
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20231004222236.411248-6-miquel.raynal%40bootlin.com
patch subject: [PATCH v11 5/7] nvmem: core: Rework layouts to become regular devices
config: sh-defconfig (https://download.01.org/0day-ci/archive/20231005/202310051638.C8Yz2WIY-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231005/202310051638.C8Yz2WIY-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/202310051638.C8Yz2WIY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/nvmem/layouts.c:19:5: warning: "CONFIG_OF" is not defined, evaluates to 0 [-Wundef]
19 | #if CONFIG_OF
| ^~~~~~~~~
vim +/CONFIG_OF +19 drivers/nvmem/layouts.c
18
> 19 #if CONFIG_OF
20 static int nvmem_layout_bus_match(struct device *dev, struct device_driver *drv)
21 {
22 return of_driver_match_device(dev, drv);
23 }
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-05 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 22:22 [PATCH v11 0/7] NVMEM cells in sysfs Miquel Raynal
2023-10-04 22:22 ` [PATCH v11 1/7] of: device: Export of_device_make_bus_id() Miquel Raynal
2023-10-04 22:22 ` [PATCH v11 2/7] nvmem: Clarify the situation when there is no DT node available Miquel Raynal
2023-10-04 22:22 ` [PATCH v11 3/7] nvmem: Move of_nvmem_layout_get_container() in another header Miquel Raynal
2023-10-05 2:47 ` kernel test robot
2023-10-05 11:37 ` kernel test robot
2023-10-04 22:22 ` [PATCH v11 4/7] nvmem: Create a header for internal sharing Miquel Raynal
2023-10-04 22:22 ` [PATCH v11 5/7] nvmem: core: Rework layouts to become regular devices Miquel Raynal
2023-10-05 8:24 ` kernel test robot [this message]
2023-10-04 22:22 ` [PATCH v11 6/7] ABI: sysfs-nvmem-cells: Expose cells through sysfs Miquel Raynal
2023-10-04 22:22 ` [PATCH v11 7/7] nvmem: core: " Miquel Raynal
2023-10-05 8:56 ` [PATCH v11 0/7] NVMEM cells in sysfs Chen-Yu Tsai
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=202310051638.C8Yz2WIY-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafal@milecki.pl \
--cc=rdunlap@infradead.org \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wenst@chromium.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).