From: kernel test robot <lkp@intel.com>
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Sebastian Reichel <sre@kernel.org>,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: [sre-misc:thinkpad-t14s-x1e 14/106] drivers/media/platform/qcom/camss/camss-csiphy.c:811:59: warning: variable 'ret' is uninitialized when used here
Date: Sat, 11 Apr 2026 05:28:46 +0800 [thread overview]
Message-ID: <202604110532.VMi9eJxS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-misc.git thinkpad-t14s-x1e
head: c368130866898c0f67e75fb8e36b0708e623553b
commit: d31e377776c34b54a5a1c50a4dcd0e19437e65e5 [14/106] media: qcom: camss: Add support for PHY API devices
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260411/202604110532.VMi9eJxS-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260411/202604110532.VMi9eJxS-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/202604110532.VMi9eJxS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/media/platform/qcom/camss/camss-csiphy.c:811:59: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
811 | dev_err(dev, "failed to get phy %s %d\n", csiphy->name, ret);
| ^~~
include/linux/dev_printk.h:154:65: note: expanded from macro 'dev_err'
154 | dev_printk_index_wrap(_dev_err, KERN_ERR, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~
include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
drivers/media/platform/qcom/camss/camss-csiphy.c:798:9: note: initialize the variable 'ret' to silence this warning
798 | int ret;
| ^
| = 0
1 warning generated.
vim +/ret +811 drivers/media/platform/qcom/camss/camss-csiphy.c
784
785 /*
786 * msm_csiphy_subdev_init - Initialize CSIPHY device structure and resources
787 * @csiphy: CSIPHY device
788 * @res: CSIPHY module resources table
789 * @id: CSIPHY module id
790 *
791 * Return 0 on success or a negative error code otherwise
792 */
793 int msm_csiphy_subdev_init(struct camss *camss,
794 struct csiphy_device *csiphy,
795 const struct camss_subdev_resources *res, u8 id)
796 {
797 struct device *dev = camss->dev;
798 int ret;
799
800 csiphy->camss = camss;
801 csiphy->id = id;
802 csiphy->cfg.combo_mode = 0;
803 csiphy->res = &res->csiphy;
804
805 snprintf(csiphy->name, ARRAY_SIZE(csiphy->name), "csiphy%d",
806 csiphy->id);
807
808 csiphy->phy = devm_phy_get(dev, csiphy->name);
809
810 if (IS_ERR(csiphy->phy)) {
> 811 dev_err(dev, "failed to get phy %s %d\n", csiphy->name, ret);
812 return PTR_ERR(csiphy->phy);
813 }
814
815 ret = phy_init(csiphy->phy);
816 if (ret)
817 dev_err(dev, "phy %s init fail %d\n", csiphy->name, ret);
818
819 return ret;
820 }
821
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-10 21:29 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=202604110532.VMi9eJxS-lkp@intel.com \
--to=lkp@intel.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sre@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