From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v7 7/7] nvmem: core: Expose cells through sysfs
Date: Wed, 9 Aug 2023 07:21:02 +0800 [thread overview]
Message-ID: <202308090730.heIvhehR-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/nvmem/core.c:2264:1: sparse: sparse: unused label 'del_cells'"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20230801182132.1058707-8-miquel.raynal@bootlin.com>
References: <20230801182132.1058707-8-miquel.raynal@bootlin.com>
TO: Miquel Raynal <miquel.raynal@bootlin.com>
Hi Miquel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.5-rc5 next-20230808]
[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/nvmem-core-Create-all-cells-before-adding-the-nvmem-device/20230802-022331
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20230801182132.1058707-8-miquel.raynal%40bootlin.com
patch subject: [PATCH v7 7/7] nvmem: core: Expose cells through sysfs
:::::: branch date: 7 days ago
:::::: commit date: 7 days ago
config: x86_64-randconfig-x062-20230808 (https://download.01.org/0day-ci/archive/20230809/202308090730.heIvhehR-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230809/202308090730.heIvhehR-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/r/202308090730.heIvhehR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/nvmem/core.c:2264:1: sparse: sparse: unused label 'del_cells'
drivers/nvmem/core.c:83:23: sparse: sparse: symbol 'nvmem_nb' was not declared. Should it be static?
vim +/del_cells +2264 drivers/nvmem/core.c
48c23a411e77cb Miquel Raynal 2023-08-01 2261
00d059fd6702f0 Miquel Raynal 2023-08-01 2262 return 0;
00d059fd6702f0 Miquel Raynal 2023-08-01 2263
48c23a411e77cb Miquel Raynal 2023-08-01 @2264 del_cells:
48c23a411e77cb Miquel Raynal 2023-08-01 2265 nvmem_device_remove_all_cells(nvmem);
00d059fd6702f0 Miquel Raynal 2023-08-01 2266 put_layout:
00d059fd6702f0 Miquel Raynal 2023-08-01 2267 nvmem_layout_put(nvmem->layout);
00d059fd6702f0 Miquel Raynal 2023-08-01 2268 return ret;
00d059fd6702f0 Miquel Raynal 2023-08-01 2269 }
00d059fd6702f0 Miquel Raynal 2023-08-01 2270
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-08 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 23:21 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 18:21 [PATCH v7 0/7] NVMEM cells in sysfs Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 7/7] nvmem: core: Expose cells through sysfs Miquel Raynal
2023-08-02 7:40 ` kernel test robot
2023-08-02 12:46 ` Miquel Raynal
2023-08-08 11:30 ` kernel test robot
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=202308090730.heIvhehR-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.