All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/3] regulator: userspace-consumer: Add regulator event support
Date: Fri, 1 Sep 2023 10:32:36 +0800	[thread overview]
Message-ID: <202309011007.XMgtARDc-lkp@intel.com> (raw)
In-Reply-To: <20230831121412.2359239-2-Naresh.Solanki@9elements.com>

Hi Naresh,

kernel test robot noticed the following build errors:

[auto build test ERROR on 35d0d2350d774fecf596cfb2fb050559fe5e1850]

url:    https://github.com/intel-lab-lkp/linux/commits/Naresh-Solanki/regulator-userspace-consumer-Add-regulator-event-support/20230831-201619
base:   35d0d2350d774fecf596cfb2fb050559fe5e1850
patch link:    https://lore.kernel.org/r/20230831121412.2359239-2-Naresh.Solanki%409elements.com
patch subject: [PATCH 2/3] regulator: userspace-consumer: Add regulator event support
config: openrisc-randconfig-r016-20230901 (https://download.01.org/0day-ci/archive/20230901/202309011007.XMgtARDc-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230901/202309011007.XMgtARDc-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/202309011007.XMgtARDc-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/regulator/userspace-consumer.c: In function 'regulator_userspace_notify':
>> drivers/regulator/userspace-consumer.c:146:47: error: initialization of 'const char * const*' from incompatible pointer type 'char *' [-Werror=incompatible-pointer-types]
     146 |         static const char * const *envp[] = { "NAME=events", NULL };
         |                                               ^~~~~~~~~~~~~
   drivers/regulator/userspace-consumer.c:146:47: note: (near initialization for 'envp[0]')
>> drivers/regulator/userspace-consumer.c:153:53: error: passing argument 3 of 'kobject_uevent_env' from incompatible pointer type [-Werror=incompatible-pointer-types]
     153 |         kobject_uevent_env(data->kobj, KOBJ_CHANGE, envp);
         |                                                     ^~~~
         |                                                     |
         |                                                     const char * const**
   In file included from include/linux/module.h:21,
                    from drivers/regulator/userspace-consumer.c:16:
   include/linux/kobject.h:214:31: note: expected 'char **' but argument is of type 'const char * const**'
     214 |                         char *envp[]);
         |                         ~~~~~~^~~~~~
   cc1: some warnings being treated as errors


vim +146 drivers/regulator/userspace-consumer.c

   139	
   140	static int regulator_userspace_notify(struct notifier_block *nb,
   141					      unsigned long event,
   142					      void *ignored)
   143	{
   144		struct userspace_consumer_data *data =
   145			container_of(nb, struct userspace_consumer_data, nb);
 > 146		static const char * const *envp[] = { "NAME=events", NULL };
   147	
   148		spin_lock(&events_lock);
   149		data->events |= event;
   150		spin_unlock(&events_lock);
   151	
   152		sysfs_notify(data->kobj, NULL, dev_attr_events.attr.name);
 > 153		kobject_uevent_env(data->kobj, KOBJ_CHANGE, envp);
   154	
   155		return NOTIFY_OK;
   156	}
   157	

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

           reply	other threads:[~2023-09-01  2:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230831121412.2359239-2-Naresh.Solanki@9elements.com>]

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=202309011007.XMgtARDc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=naresh.solanki@9elements.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.