public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vijayanand Jitta <vijayanand.jitta@oss.qualcomm.com>,
	robin.murphy@arm.com, will@kernel.org, joro@8bytes.org,
	robh@kernel.org, dmitry.baryshkov@oss.qualcomm.com,
	konrad.dybcio@oss.qualcomm.com, bjorn.andersson@oss.qualcomm.com,
	bod@kernel.org, conor+dt@kernel.org, krzk+dt@kernel.org,
	saravanak@google.com, prakash.gupta@oss.qualcomm.com,
	vikash.garodia@oss.qualcomm.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Charan Teja Kalla <charan.kalla@oss.qualcomm.com>,
	Vijayanand Jitta <vijayanand.jitta@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/3] of: factor arguments passed to of_map_id() into a struct
Date: Wed, 24 Dec 2025 11:37:15 +0800	[thread overview]
Message-ID: <202512241124.Tl95CT1C-lkp@intel.com> (raw)
In-Reply-To: <20251221213602.2413124-3-vijayanand.jitta@oss.qualcomm.com>

Hi Vijayanand,

kernel test robot noticed the following build warnings:

[auto build test WARNING on xen-tip/linux-next]
[cannot apply to robh/for-next pci/next pci/for-linus linus/master v6.19-rc2 next-20251219]
[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/Vijayanand-Jitta/of-Add-convenience-wrappers-for-of_map_id/20251222-053941
base:   https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
patch link:    https://lore.kernel.org/r/20251221213602.2413124-3-vijayanand.jitta%40oss.qualcomm.com
patch subject: [PATCH v3 2/3] of: factor arguments passed to of_map_id() into a struct
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20251224/202512241124.Tl95CT1C-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 4ef602d446057dabf5f61fb221669ecbeda49279)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512241124.Tl95CT1C-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/202512241124.Tl95CT1C-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/of/base.c:2078:71: warning: address of array 'arg->map_args.args' will always evaluate to 'true' [-Wpointer-bool-conversion]
    2078 |         if (!np || !map_name || !arg || (!arg->map_args.np && !arg->map_args.args))
         |                                                               ~~~~~~~~~~~~~~~^~~~
   drivers/of/base.c:2136:21: warning: address of array 'arg->map_args.args' will always evaluate to 'true' [-Wpointer-bool-conversion]
    2136 |                 if (arg->map_args.args)
         |                 ~~  ~~~~~~~~~~~~~~^~~~
   drivers/of/base.c:2149:20: warning: address of array 'arg->map_args.args' will always evaluate to 'true' [-Wpointer-bool-conversion]
    2149 |         if (arg->map_args.args)
         |         ~~  ~~~~~~~~~~~~~~^~~~
   3 warnings generated.


vim +2078 drivers/of/base.c

  2047	
  2048	/**
  2049	 * of_map_id - Translate an ID through a downstream mapping.
  2050	 * @np: root complex device node.
  2051	 * @id: device ID to map.
  2052	 * @map_name: property name of the map to use.
  2053	 * @map_mask_name: optional property name of the mask to use.
  2054	 * @arg: contains the optional params, wrapped in a struct of_phandle_args,
  2055	 *	which includes:
  2056	 *	np: pointer to the target device node
  2057	 *	args_count: number of arguments
  2058	 *	args[]: array to receive the translated ID(s).
  2059	 *
  2060	 * Given a device ID, look up the appropriate implementation-defined
  2061	 * platform ID and/or the target device which receives transactions on that
  2062	 * ID, as per the "iommu-map" and "msi-map" bindings. Either of @target or
  2063	 * @id_out may be NULL if only the other is required. If @target points to
  2064	 * a non-NULL device node pointer, only entries targeting that node will be
  2065	 * matched; if it points to a NULL value, it will receive the device node of
  2066	 * the first matching target phandle, with a reference held.
  2067	 *
  2068	 * Return: 0 on success or a standard error code on failure.
  2069	 */
  2070	int of_map_id(const struct device_node *np, u32 id,
  2071		       const char *map_name, const char *map_mask_name,
  2072		       struct of_map_id_arg *arg)
  2073	{
  2074		u32 map_mask, masked_id;
  2075		int map_len;
  2076		const __be32 *map = NULL;
  2077	
> 2078		if (!np || !map_name || !arg || (!arg->map_args.np && !arg->map_args.args))

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

  reply	other threads:[~2025-12-24  3:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 21:35 [PATCH v3 0/3] of: parsing of multi #{iommu,msi}-cells in maps Vijayanand Jitta
2025-12-21 21:36 ` [PATCH v3 1/3] of: Add convenience wrappers for of_map_id() Vijayanand Jitta
2025-12-30 15:29   ` Frank Li
2025-12-21 21:36 ` [PATCH v3 2/3] of: factor arguments passed to of_map_id() into a struct Vijayanand Jitta
2025-12-24  3:37   ` kernel test robot [this message]
2025-12-24  3:37   ` kernel test robot
2025-12-21 21:36 ` [PATCH v3 3/3] of: Respect #{iommu,msi}-cells in maps Vijayanand Jitta

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=202512241124.Tl95CT1C-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=bod@kernel.org \
    --cc=charan.kalla@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=prakash.gupta@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=saravanak@google.com \
    --cc=vijayanand.jitta@oss.qualcomm.com \
    --cc=vikash.garodia@oss.qualcomm.com \
    --cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox