From: kernel test robot <lkp@intel.com>
To: Sunil V L <sunilvl@oss.qualcomm.com>
Cc: oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_trace_acpi_support_v1 82/84] drivers/acpi/property.c:1995:44: warning: unused variable 'port'
Date: Sat, 03 Oct 2026 01:50:36 +0200 [thread overview]
Message-ID: <202610030122.dLkViI4M-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_trace_acpi_support_v1
head: c27eb336790d72160ea5ab7997d0dd01bb230e96
commit: 07c38c2b100fdff5878133f41eb7875af40ab366 [82/84] ACPI: property: Add device graph support
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261003/202610030122.dLkViI4M-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261003/202610030122.dLkViI4M-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/202610030122.dLkViI4M-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/acpi/property.c: In function 'acpi_graph_get_remote_directional_port':
>> drivers/acpi/property.c:1995:44: warning: unused variable 'port' [-Wunused-variable]
1995 | struct fwnode_handle *ports_node, *port;
| ^~~~
--
>> Warning: drivers/acpi/property.c:1993 function parameter 'ports_name' not described in 'acpi_graph_get_remote_directional_port'
>> Warning: drivers/acpi/property.c:1993 function parameter 'ports_name' not described in 'acpi_graph_get_remote_directional_port'
vim +/port +1995 drivers/acpi/property.c
1981
1982 /**
1983 * acpi_graph_get_remote_directional_port - Find a port nested under a
1984 * synthetic "in-ports"/"out-ports" root node
1985 * @fwnode: device fwnode
1986 * @port_nr: the desired port number
1987 *
1988 * Return: the port node on success, NULL otherwise.
1989 */
1990 static struct fwnode_handle *
1991 acpi_graph_get_remote_directional_port(struct fwnode_handle *fwnode,
1992 unsigned int port_nr,
> 1993 const char *ports_name)
1994 {
> 1995 struct fwnode_handle *ports_node, *port;
1996
1997 if (!ports_name)
1998 return NULL;
1999
2000 ports_node = acpi_fwnode_get_named_child_node(fwnode, ports_name);
2001 if (ports_node)
2002 return acpi_graph_get_child_prop_value(ports_node, "port", port_nr);
2003
2004 return NULL;
2005 }
2006
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-02 23:51 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=202610030122.dLkViI4M-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sunilvl@oss.qualcomm.com \
/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.