From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v10 2/2] phy: Add Google Tensor SoC USB PHY driver
Date: Mon, 29 Dec 2025 20:06:10 +0800 [thread overview]
Message-ID: <202512291900.LsAM5AIl-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251227-phyb4-v10-2-e8caf6b93fe7@google.com>
References: <20251227-phyb4-v10-2-e8caf6b93fe7@google.com>
TO: Roy Luo <royluo@google.com>
TO: Vinod Koul <vkoul@kernel.org>
TO: Kishon Vijay Abraham I <kishon@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Peter Griffin <peter.griffin@linaro.org>
TO: "André Draszik" <andre.draszik@linaro.org>
TO: Tudor Ambarus <tudor.ambarus@linaro.org>
TO: Philipp Zabel <p.zabel@pengutronix.de>
TO: Neil Armstrong <neil.armstrong@linaro.org>
CC: Badhri Jagan Sridharan <badhri@google.com>
CC: Doug Anderson <dianders@google.com>
CC: linux-phy@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-samsung-soc@vger.kernel.org
CC: Joy Chakraborty <joychakr@google.com>
CC: Naveen Kumar <mnkumar@google.com>
CC: Roy Luo <royluo@google.com>
Hi Roy,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3f0e9c8cefa913dd9bd1d79b9a68896ea130f106]
url: https://github.com/intel-lab-lkp/linux/commits/Roy-Luo/dt-bindings-phy-google-Add-Google-Tensor-G5-USB-PHY/20251227-085610
base: 3f0e9c8cefa913dd9bd1d79b9a68896ea130f106
patch link: https://lore.kernel.org/r/20251227-phyb4-v10-2-e8caf6b93fe7%40google.com
patch subject: [PATCH v10 2/2] phy: Add Google Tensor SoC USB PHY driver
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: xtensa-randconfig-r072-20251229 (https://download.01.org/0day-ci/archive/20251229/202512291900.LsAM5AIl-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 8.5.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202512291900.LsAM5AIl-lkp@intel.com/
smatch warnings:
drivers/phy/phy-google-usb.c:86 google_usb_set_orientation() error: 'gphy' dereferencing possible ERR_PTR()
vim +/gphy +86 drivers/phy/phy-google-usb.c
b9930f0c8b336e Roy Luo 2025-12-27 78
b9930f0c8b336e Roy Luo 2025-12-27 79 static int google_usb_set_orientation(struct typec_switch_dev *sw,
b9930f0c8b336e Roy Luo 2025-12-27 80 enum typec_orientation orientation)
b9930f0c8b336e Roy Luo 2025-12-27 81 {
b9930f0c8b336e Roy Luo 2025-12-27 82 struct google_usb_phy *gphy = typec_switch_get_drvdata(sw);
b9930f0c8b336e Roy Luo 2025-12-27 83
b9930f0c8b336e Roy Luo 2025-12-27 84 dev_dbg(gphy->dev, "set orientation %d\n", orientation);
b9930f0c8b336e Roy Luo 2025-12-27 85
b9930f0c8b336e Roy Luo 2025-12-27 @86 gphy->orientation = orientation;
b9930f0c8b336e Roy Luo 2025-12-27 87
b9930f0c8b336e Roy Luo 2025-12-27 88 if (pm_runtime_suspended(gphy->dev))
b9930f0c8b336e Roy Luo 2025-12-27 89 return 0;
b9930f0c8b336e Roy Luo 2025-12-27 90
b9930f0c8b336e Roy Luo 2025-12-27 91 guard(mutex)(&gphy->phy_mutex);
b9930f0c8b336e Roy Luo 2025-12-27 92
b9930f0c8b336e Roy Luo 2025-12-27 93 set_vbus_valid(gphy);
b9930f0c8b336e Roy Luo 2025-12-27 94
b9930f0c8b336e Roy Luo 2025-12-27 95 return 0;
b9930f0c8b336e Roy Luo 2025-12-27 96 }
b9930f0c8b336e Roy Luo 2025-12-27 97
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-29 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 12:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-27 0:53 [PATCH v10 0/2] Add Google Tensor SoC USB PHY support Roy Luo
2025-12-27 0:53 ` [PATCH v10 2/2] phy: Add Google Tensor SoC USB PHY driver Roy Luo
2025-12-27 0:53 ` Roy Luo
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=202512291900.LsAM5AIl-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@lists.linux.dev \
/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.