From: Charan Teja Kalla <charan.kalla@oss.qualcomm.com>
To: kernel test robot <lkp@intel.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
Subject: Re: [PATCH 5/6] of: add infra to parse iommu-map per IOMMU cell count
Date: Tue, 4 Nov 2025 16:27:12 +0530 [thread overview]
Message-ID: <2dd128f2-d41f-4eda-a393-260098749a07@oss.qualcomm.com> (raw)
In-Reply-To: <202511041853.IxYgvWlc-lkp@intel.com>
On 11/4/2025 4:16 PM, kernel test robot wrote:
>>> drivers/of/base.c:2127:6: warning: variable 'legacy_iommu_cells' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
> 2127 | if (map_len % 4 != 0)
> | ^~~~~~~~~~~~~~~~
> drivers/of/base.c:2130:9: note: uninitialized use occurs here
> 2130 | return legacy_iommu_cells ? : of_iommu_map_id_actual_cell_count(map, map_len, cells);
> | ^~~~~~~~~~~~~~~~~~
> drivers/of/base.c:2127:2: note: remove the 'if' if its condition is always true
> 2127 | if (map_len % 4 != 0)
> | ^~~~~~~~~~~~~~~~~~~~~
> 2128 | legacy_iommu_cells = of_iommu_map_id_legacy_cell_count(map, map_len);
> drivers/of/base.c:2125:24: note: initialize the variable 'legacy_iommu_cells' to silence this warning
> 2125 | u32 legacy_iommu_cells;
> | ^
> | = 0
> 1 warning generated.
Will wait for additional comments and take care of this in the next spin.
prev parent reply other threads:[~2025-11-04 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74d4ddf90c0fb485fda1feec5116dc38e5fd23cf.1762235099.git.charan.kalla@oss.qualcomm.com>
2025-11-04 10:46 ` [PATCH 5/6] of: add infra to parse iommu-map per IOMMU cell count kernel test robot
2025-11-04 10:57 ` Charan Teja Kalla [this message]
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=2dd128f2-d41f-4eda-a393-260098749a07@oss.qualcomm.com \
--to=charan.kalla@oss.qualcomm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=bod@kernel.org \
--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=lkp@intel.com \
--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=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