From: kernel test robot <lkp@intel.com>
To: Josua Mayer <josua@solid-run.com>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org, Josua Mayer <josua@solid-run.com>
Subject: Re: [PATCH v2] phy: mvebu-cp110-utmi: support swapping d+/d- lanes by dts property
Date: Wed, 4 Sep 2024 01:50:57 +0800 [thread overview]
Message-ID: <202409040139.hNh9K4iF-lkp@intel.com> (raw)
In-Reply-To: <20240903-mvebu-utmi-phy-v2-1-7f49c131fad0@solid-run.com>
Hi Josua,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8400291e289ee6b2bf9779ff1c83a291501f017b]
url: https://github.com/intel-lab-lkp/linux/commits/Josua-Mayer/phy-mvebu-cp110-utmi-support-swapping-d-d-lanes-by-dts-property/20240903-164826
base: 8400291e289ee6b2bf9779ff1c83a291501f017b
patch link: https://lore.kernel.org/r/20240903-mvebu-utmi-phy-v2-1-7f49c131fad0%40solid-run.com
patch subject: [PATCH v2] phy: mvebu-cp110-utmi: support swapping d+/d- lanes by dts property
config: arc-randconfig-r071-20240903 (https://download.01.org/0day-ci/archive/20240904/202409040139.hNh9K4iF-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240904/202409040139.hNh9K4iF-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/202409040139.hNh9K4iF-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/phy/marvell/phy-mvebu-cp110-utmi.c:110: warning: Function parameter or struct member 'swap_dx' not described in 'mvebu_cp110_utmi_port'
vim +110 drivers/phy/marvell/phy-mvebu-cp110-utmi.c
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 97
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 98 /**
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 99 * struct mvebu_cp110_utmi_port - PHY port data
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 100 *
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 101 * @priv: PHY driver data
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 102 * @id: PHY port ID
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 103 * @dr_mode: PHY connection: USB_DR_MODE_HOST or USB_DR_MODE_PERIPHERAL
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 104 */
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 105 struct mvebu_cp110_utmi_port {
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 106 struct mvebu_cp110_utmi *priv;
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 107 u32 id;
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 108 enum usb_dr_mode dr_mode;
7208af25e8a67e Josua Mayer 2024-09-03 109 bool swap_dx;
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 @110 };
2fc989f74b8dac Konstantin Porotchkin 2021-03-07 111
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-03 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:41 Josua Mayer
2024-09-03 17:50 ` kernel test robot [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=202409040139.hNh9K4iF-lkp@intel.com \
--to=lkp@intel.com \
--cc=josua@solid-run.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®