[phy:next 47/52] Warning: drivers/phy/rockchip/phy-rockchip-inno-usb2.c:184 struct member 'clkout_ctl_phy' not described in 'rockchip_usb2phy_cfg'

All of lore.kernel.org
 help / color / mirror / Atom feed

From: kernel test robot <lkp@intel.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: oe-kbuild-all@lists.linux.dev, Vinod Koul <vkoul@kernel.org>,
	Kishon <kishon@ti.com>, Heiko Stuebner <heiko@sntech.de>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: [phy:next 47/52] Warning: drivers/phy/rockchip/phy-rockchip-inno-usb2.c:184 struct member 'clkout_ctl_phy' not described in 'rockchip_usb2phy_cfg'
Date: Fri, 15 May 2026 03:50:42 +0800	[thread overview]
Message-ID: <202605150315.MyBNQOPB-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
head:   fd6cd05ceabdf67635a4cef5145f79d1217bf11b
commit: 2775541de0580ab1cd077dfef710e6316563d567 [47/52] phy: rockchip: inno-usb2: Add clkout_ctl_phy support
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20260515/202605150315.MyBNQOPB-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605150315.MyBNQOPB-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/202605150315.MyBNQOPB-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: drivers/phy/rockchip/phy-rockchip-inno-usb2.c:184 struct member 'clkout_ctl_phy' not described in 'rockchip_usb2phy_cfg'
>> Warning: drivers/phy/rockchip/phy-rockchip-inno-usb2.c:184 struct member 'clkout_ctl_phy' not described in 'rockchip_usb2phy_cfg'

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

                 reply	other threads:[~2026-05-14 19: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=202605150315.MyBNQOPB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=kishon@ti.com \
    --cc=neil.armstrong@linaro.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vkoul@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 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.