linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: [rafael-pm:bleeding-edge 6/11] drivers/base/swnode.c:1120:29: error: too many arguments to function call, expected single argument 'dev', have 2 arguments
Date: Thu, 16 Sep 2021 10:02:11 +0800	[thread overview]
Message-ID: <202109161004.P6Jbe7L8-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3476 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head:   9808623e1bba7d929b50865d7e2d7042cd4e5e7b
commit: 810fc8571f8b70a4263266d979f97edec2804574 [6/11] software node: balance refcount for managed sw nodes
config: x86_64-randconfig-a002-20210916 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 8cbbd7e0b2aa21ce7e416cfb63d9965518948c35)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=810fc8571f8b70a4263266d979f97edec2804574
        git remote add rafael-pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
        git fetch --no-tags rafael-pm bleeding-edge
        git checkout 810fc8571f8b70a4263266d979f97edec2804574
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/base/swnode.c:1120:29: error: too many arguments to function call, expected single argument 'dev', have 2 arguments
                   software_node_notify(dev, KOBJ_ADD);
                   ~~~~~~~~~~~~~~~~~~~~      ^~~~~~~~
   drivers/base/base.h:206:6: note: 'software_node_notify' declared here
   void software_node_notify(struct device *dev);
        ^
   1 error generated.


vim +/dev +1120 drivers/base/swnode.c

  1085	
  1086	/**
  1087	 * device_create_managed_software_node - Create a software node for a device
  1088	 * @dev: The device the software node is assigned to.
  1089	 * @properties: Device properties for the software node.
  1090	 * @parent: Parent of the software node.
  1091	 *
  1092	 * Creates a software node as a managed resource for @dev, which means the
  1093	 * lifetime of the newly created software node is tied to the lifetime of @dev.
  1094	 * Software nodes created with this function should not be reused or shared
  1095	 * because of that. The function takes a deep copy of @properties for the
  1096	 * software node.
  1097	 *
  1098	 * Since the new software node is assigned directly to @dev, and since it should
  1099	 * not be shared, it is not returned to the caller. The function returns 0 on
  1100	 * success, and errno in case of an error.
  1101	 */
  1102	int device_create_managed_software_node(struct device *dev,
  1103						const struct property_entry *properties,
  1104						const struct software_node *parent)
  1105	{
  1106		struct fwnode_handle *p = software_node_fwnode(parent);
  1107		struct fwnode_handle *fwnode;
  1108	
  1109		if (parent && !p)
  1110			return -EINVAL;
  1111	
  1112		fwnode = fwnode_create_software_node(properties, p);
  1113		if (IS_ERR(fwnode))
  1114			return PTR_ERR(fwnode);
  1115	
  1116		to_swnode(fwnode)->managed = true;
  1117		set_secondary_fwnode(dev, fwnode);
  1118	
  1119		if (device_is_registered(dev))
> 1120			software_node_notify(dev, KOBJ_ADD);
  1121	
  1122		return 0;
  1123	}
  1124	EXPORT_SYMBOL_GPL(device_create_managed_software_node);
  1125	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33918 bytes --]

                 reply	other threads:[~2021-09-16  2:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202109161004.P6Jbe7L8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devel@acpica.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=rjw@rjwysocki.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).