All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
	Sebastian Reichel <sre@kernel.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Daniel Lezcano" <daniel.lezcano@linaro.org>,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Lukasz Luba" <lukasz.luba@arm.com>,
	linux-pm@vger.kernel.org, "Søren Andersen" <san@skov.dk>
Subject: Re: [PATCH v4 4/7] nvmem: add support for device and sysfs-based cell lookups
Date: Sun, 9 Mar 2025 01:06:39 +0800	[thread overview]
Message-ID: <202503090029.GNYIypVB-lkp@intel.com> (raw)
In-Reply-To: <20250306093900.2199442-5-o.rempel@pengutronix.de>

Hi Oleksij,

kernel test robot noticed the following build warnings:

[auto build test WARNING on sre-power-supply/for-next]
[also build test WARNING on broonie-regulator/for-next rafael-pm/thermal linus/master v6.14-rc5 next-20250307]
[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/Oleksij-Rempel/power-Extend-power_on_reason-h-for-upcoming-PSCRR-framework/20250306-174233
base:   https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
patch link:    https://lore.kernel.org/r/20250306093900.2199442-5-o.rempel%40pengutronix.de
patch subject: [PATCH v4 4/7] nvmem: add support for device and sysfs-based cell lookups
config: hexagon-randconfig-002-20250308 (https://download.01.org/0day-ci/archive/20250309/202503090029.GNYIypVB-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e15545cad8297ec7555f26e5ae74a9f0511203e7)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250309/202503090029.GNYIypVB-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/202503090029.GNYIypVB-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/rtc/rtc-pm8xxx.c:10:
>> include/linux/nvmem-consumer.h:115:20: warning: no previous prototype for function 'nvmem_cell_get_by_sysfs_name' [-Wmissing-prototypes]
     115 | struct nvmem_cell *nvmem_cell_get_by_sysfs_name(struct nvmem_device *nvmem,
         |                    ^
   include/linux/nvmem-consumer.h:115:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
     115 | struct nvmem_cell *nvmem_cell_get_by_sysfs_name(struct nvmem_device *nvmem,
         | ^
         | static 
>> include/linux/nvmem-consumer.h:197:22: warning: no previous prototype for function 'nvmem_device_get_by_name' [-Wmissing-prototypes]
     197 | struct nvmem_device *nvmem_device_get_by_name(const char *name)
         |                      ^
   include/linux/nvmem-consumer.h:197:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
     197 | struct nvmem_device *nvmem_device_get_by_name(const char *name)
         | ^
         | static 
   2 warnings generated.


vim +/nvmem_cell_get_by_sysfs_name +115 include/linux/nvmem-consumer.h

   114	
 > 115	struct nvmem_cell *nvmem_cell_get_by_sysfs_name(struct nvmem_device *nvmem,
   116							const char *cell_name)
   117	{
   118		return ERR_PTR(-EOPNOTSUPP);
   119	}
   120	
   121	static inline void devm_nvmem_cell_put(struct device *dev,
   122					       struct nvmem_cell *cell)
   123	{
   124	
   125	}
   126	static inline void nvmem_cell_put(struct nvmem_cell *cell)
   127	{
   128	}
   129	
   130	static inline void *nvmem_cell_read(struct nvmem_cell *cell, size_t *len)
   131	{
   132		return ERR_PTR(-EOPNOTSUPP);
   133	}
   134	
   135	static inline int nvmem_cell_write(struct nvmem_cell *cell,
   136					   void *buf, size_t len)
   137	{
   138		return -EOPNOTSUPP;
   139	}
   140	
   141	static inline int nvmem_cell_get_size(struct nvmem_cell *cell, size_t *bytes,
   142					      size_t *bits)
   143	{
   144		return -EOPNOTSUPP;
   145	}
   146	
   147	static inline int nvmem_cell_read_u8(struct device *dev,
   148					     const char *cell_id, u8 *val)
   149	{
   150		return -EOPNOTSUPP;
   151	}
   152	
   153	static inline int nvmem_cell_read_u16(struct device *dev,
   154					      const char *cell_id, u16 *val)
   155	{
   156		return -EOPNOTSUPP;
   157	}
   158	
   159	static inline int nvmem_cell_read_u32(struct device *dev,
   160					      const char *cell_id, u32 *val)
   161	{
   162		return -EOPNOTSUPP;
   163	}
   164	
   165	static inline int nvmem_cell_read_u64(struct device *dev,
   166					      const char *cell_id, u64 *val)
   167	{
   168		return -EOPNOTSUPP;
   169	}
   170	
   171	static inline int nvmem_cell_read_variable_le_u32(struct device *dev,
   172							 const char *cell_id,
   173							 u32 *val)
   174	{
   175		return -EOPNOTSUPP;
   176	}
   177	
   178	static inline int nvmem_cell_read_variable_le_u64(struct device *dev,
   179							  const char *cell_id,
   180							  u64 *val)
   181	{
   182		return -EOPNOTSUPP;
   183	}
   184	
   185	static inline struct nvmem_device *nvmem_device_get(struct device *dev,
   186							    const char *name)
   187	{
   188		return ERR_PTR(-EOPNOTSUPP);
   189	}
   190	
   191	static inline struct nvmem_device *devm_nvmem_device_get(struct device *dev,
   192								 const char *name)
   193	{
   194		return ERR_PTR(-EOPNOTSUPP);
   195	}
   196	
 > 197	struct nvmem_device *nvmem_device_get_by_name(const char *name)
   198	{
   199		return ERR_PTR(-EOPNOTSUPP);
   200	}
   201	

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

  parent reply	other threads:[~2025-03-08 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06  9:38 [PATCH v4 0/7] Introduction of PSCR Framework and Related Components Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 1/7] power: Extend power_on_reason.h for upcoming PSCRR framework Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 2/7] power: reset: Introduce PSCR Recording Framework for Non-Volatile Storage Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 3/7] nvmem: provide consumer access to cell size metrics Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 4/7] nvmem: add support for device and sysfs-based cell lookups Oleksij Rempel
2025-03-07 12:35   ` kernel test robot
2025-03-07 15:04   ` kernel test robot
2025-03-08 17:06   ` kernel test robot [this message]
2025-03-06  9:38 ` [PATCH v4 5/7] power: reset: add PSCR NVMEM Driver for Recording Power State Change Reasons Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 6/7] regulator: set Power State Change Reason before hw_protection_shutdown() Oleksij Rempel
2025-03-06  9:38 ` [PATCH v4 7/7] thermal: core: Record PSCR " Oleksij Rempel
2025-03-12 15:35   ` Daniel Lezcano
2025-03-12 16:51     ` Oleksij Rempel
2025-03-12 17:22       ` Daniel Lezcano

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=202503090029.GNYIypVB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lukasz.luba@arm.com \
    --cc=o.rempel@pengutronix.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=san@skov.dk \
    --cc=sre@kernel.org \
    --cc=srinivas.kandagatla@linaro.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 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.