All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v12 7/7] nvmem: core: Expose cells through sysfs
Date: Sat, 7 Oct 2023 02:47:30 +0800	[thread overview]
Message-ID: <202310070203.rNhXeE2Q-lkp@intel.com> (raw)
In-Reply-To: <20231005155907.2701706-8-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-20231006]
[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/20231006-000111
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:    https://lore.kernel.org/r/20231005155907.2701706-8-miquel.raynal%40bootlin.com
patch subject: [PATCH v12 7/7] nvmem: core: Expose cells through sysfs
config: m68k-m5208evb_defconfig (https://download.01.org/0day-ci/archive/20231007/202310070203.rNhXeE2Q-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231007/202310070203.rNhXeE2Q-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/202310070203.rNhXeE2Q-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/nvmem/core.c:22:
   drivers/nvmem/internals.h: In function 'nvmem_destroy_layout':
   drivers/nvmem/internals.h:55:47: error: no return statement in function returning non-void [-Werror=return-type]
      55 | static inline int nvmem_destroy_layout(struct nvmem_device *nvmem) { }
         |                                               ^~~~~~~~~~~~
   drivers/nvmem/core.c: In function 'nvmem_register':
>> drivers/nvmem/core.c:1045:1: warning: label 'err_remove_dev' defined but not used [-Wunused-label]
    1045 | err_remove_dev:
         | ^~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/err_remove_dev +1045 drivers/nvmem/core.c

  1040	
  1041		blocking_notifier_call_chain(&nvmem_notifier, NVMEM_ADD, nvmem);
  1042	
  1043		return nvmem;
  1044	
> 1045	err_remove_dev:
  1046		device_del(&nvmem->dev);
  1047	err_destroy_layout:
  1048		nvmem_destroy_layout(nvmem);
  1049	err_remove_cells:
  1050		nvmem_device_remove_all_cells(nvmem);
  1051		if (config->compat)
  1052			nvmem_sysfs_remove_compat(nvmem, config);
  1053	err_put_device:
  1054		put_device(&nvmem->dev);
  1055	
  1056		return ERR_PTR(rval);
  1057	}
  1058	EXPORT_SYMBOL_GPL(nvmem_register);
  1059	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-10-06 18:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 15:59 [PATCH v12 0/7] NVMEM cells in sysfs Miquel Raynal
2023-10-05 15:59 ` [PATCH v12 1/7] of: device: Export of_device_make_bus_id() Miquel Raynal
2023-10-06 17:02   ` Rob Herring
2023-10-05 15:59 ` [PATCH v12 2/7] nvmem: Clarify the situation when there is no DT node available Miquel Raynal
2023-10-06 11:41   ` Rafał Miłecki
2023-10-06 16:32     ` Miquel Raynal
2023-10-07 16:09       ` Rafał Miłecki
2023-10-08 13:39         ` Miquel Raynal
2023-10-09  9:44       ` Srinivas Kandagatla
2023-10-05 15:59 ` [PATCH v12 3/7] nvmem: Move of_nvmem_layout_get_container() in another header Miquel Raynal
2023-10-05 15:59 ` [PATCH v12 4/7] nvmem: Create a header for internal sharing Miquel Raynal
2023-10-05 15:59 ` [PATCH v12 5/7] nvmem: core: Rework layouts to become regular devices Miquel Raynal
2023-10-06 11:49   ` Rafał Miłecki
2023-10-06 16:33     ` Miquel Raynal
2023-10-07 16:31   ` Greg Kroah-Hartman
2023-10-11 10:33     ` Miquel Raynal
2023-10-08 13:42   ` kernel test robot
2023-10-09  9:44   ` Srinivas Kandagatla
2023-10-11  7:38     ` Miquel Raynal
2023-10-11 10:02       ` Srinivas Kandagatla
2023-10-11 10:58         ` Miquel Raynal
2023-10-05 15:59 ` [PATCH v12 6/7] ABI: sysfs-nvmem-cells: Expose cells through sysfs Miquel Raynal
2023-10-05 15:59 ` [PATCH v12 7/7] nvmem: core: " Miquel Raynal
2023-10-06 18:47   ` kernel test robot [this message]
2023-10-09  9:48   ` Srinivas Kandagatla
2023-10-11  7:15     ` Miquel Raynal
2023-10-11  8:27       ` Srinivas Kandagatla
2023-10-11  8:33         ` Miquel Raynal
2023-10-11  8:45           ` Srinivas Kandagatla
2023-10-11  8:58             ` Miquel Raynal
2023-10-11  9:26               ` Srinivas Kandagatla
2023-10-11  9:44                 ` Miquel Raynal
2023-10-11 10:02                   ` Srinivas Kandagatla
2023-10-11 11:09                     ` Miquel Raynal
2023-10-11 13:56                       ` Srinivas Kandagatla
2023-10-11 14:02                         ` Miquel Raynal

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=202310070203.rNhXeE2Q-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=oe-kbuild-all@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.