All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v7 7/7] nvmem: core: Expose cells through sysfs
Date: Wed, 2 Aug 2023 14:46:42 +0200	[thread overview]
Message-ID: <20230802144642.3d003c2e@xps-13> (raw)
In-Reply-To: <202308021505.FG8g7tZG-lkp@intel.com>

Hello,

lkp@intel.com wrote on Wed, 2 Aug 2023 15:40:10 +0800:

> 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-rc4 next-20230801]
> [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
> config: x86_64-randconfig-x005-20230731 (https://download.01.org/0day-ci/archive/20230802/202308021505.FG8g7tZG-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce: (https://download.01.org/0day-ci/archive/20230802/202308021505.FG8g7tZG-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/202308021505.FG8g7tZG-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
> >> drivers/nvmem/core.c:2264:1: warning: unused label 'del_cells' [-Wunused-label]  
>    del_cells:
>    ^~~~~~~~~~
>    1 warning generated.

This warning triggers with CONFIG_NVMEM_SYSFS=n, I'll fix that.
I'll wait a bit anyway to get some feedback about the new approach.

> 
> 
> vim +/del_cells +2264 drivers/nvmem/core.c
> 
>   2261	
>   2262		return 0;
>   2263	
> > 2264	del_cells:  
>   2265		nvmem_device_remove_all_cells(nvmem);
>   2266	put_layout:
>   2267		nvmem_layout_put(nvmem->layout);
>   2268		return ret;
>   2269	}
>   2270	
> 


Thanks,
Miquèl

  reply	other threads:[~2023-08-02 12:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 18:21 [PATCH v7 0/7] NVMEM cells in sysfs Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 1/7] nvmem: core: Create all cells before adding the nvmem device Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 2/7] nvmem: core: Do not open-code existing functions Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 3/7] nvmem: core: Track the registered devices Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 4/7] nvmem: core: Notify when a new layout is registered Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 5/7] nvmem: core: Rework layouts to become platform devices Miquel Raynal
2023-08-03 10:13   ` Dan Carpenter
2023-08-04 15:39     ` Miquel Raynal
2023-08-04 15:46       ` Miquel Raynal
2023-08-04 16:05         ` Dan Carpenter
2023-08-04 16:47           ` Miquel Raynal
2023-08-04 16:02       ` Dan Carpenter
2023-08-01 18:21 ` [PATCH v7 6/7] ABI: sysfs-nvmem-cells: Expose cells through sysfs Miquel Raynal
2023-08-05 14:50   ` Daniel Golle
2023-08-07  7:20     ` Miquel Raynal
2023-08-01 18:21 ` [PATCH v7 7/7] nvmem: core: " Miquel Raynal
2023-08-02  7:40   ` kernel test robot
2023-08-02 12:46     ` Miquel Raynal [this message]
2023-08-08 11:30   ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2023-08-08 23:21 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=20230802144642.3d003c2e@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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.