From: kernel test robot <lkp@intel.com>
To: Karthik Poduval <kpoduval@lab126.com>,
jyxiong@amazon.com, miguel.lopes@synopsys.com,
anishkmr@amazon.com, vkoul@kernel.org, kishon@kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Karthik Poduval <kpoduval@lab126.com>
Subject: Re: [PATCH v2 1/2] phy: dw-dphy-rx: Add Synopsys DesignWare D-PHY RX
Date: Fri, 11 Jul 2025 15:13:13 +0800 [thread overview]
Message-ID: <202507111412.83Oiz7hO-lkp@intel.com> (raw)
In-Reply-To: <2383f8cf2a8f5e1b914d4cf9bd11674ed55876d2.1752106239.git.kpoduval@lab126.com>
Hi Karthik,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.16-rc5 next-20250710]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Karthik-Poduval/phy-dw-dphy-rx-Add-Synopsys-DesignWare-D-PHY-RX/20250710-104505
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/2383f8cf2a8f5e1b914d4cf9bd11674ed55876d2.1752106239.git.kpoduval%40lab126.com
patch subject: [PATCH v2 1/2] phy: dw-dphy-rx: Add Synopsys DesignWare D-PHY RX
config: sparc-randconfig-r123-20250711 (https://download.01.org/0day-ci/archive/20250711/202507111412.83Oiz7hO-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 12.4.0
reproduce: (https://download.01.org/0day-ci/archive/20250711/202507111412.83Oiz7hO-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/202507111412.83Oiz7hO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/phy/phy-dw-dphy.c:112:24: sparse: sparse: symbol 'range_gen3' was not declared. Should it be static?
>> drivers/phy/phy-dw-dphy.c:427:24: sparse: sparse: symbol 'dw_dphy_1p2' was not declared. Should it be static?
vim +/range_gen3 +112 drivers/phy/phy-dw-dphy.c
107
108 /*
109 * DW DPHY Gen3 calibration table
110 *
111 */
> 112 struct range_dphy_gen3 range_gen3[] = {
113 { 80, 0b0000000, 460 }, { 90, 0b0010000, 460 },
114 { 100, 0b0100000, 460 }, { 110, 0b0110000, 460 },
115 { 120, 0b0000001, 460 }, { 130, 0b0010001, 460 },
116 { 140, 0b0100001, 460 }, { 150, 0b0110001, 460 },
117 { 160, 0b0000010, 460 }, { 170, 0b0010010, 460 },
118 { 180, 0b0100010, 460 }, { 190, 0b0110010, 460 },
119 { 205, 0b0000011, 460 }, { 220, 0b0010011, 460 },
120 { 235, 0b0100011, 460 }, { 250, 0b0110011, 460 },
121 { 275, 0b0000100, 460 }, { 300, 0b0010100, 460 },
122 { 325, 0b0100101, 460 }, { 350, 0b0110101, 460 },
123 { 400, 0b0000101, 460 }, { 450, 0b0010110, 460 },
124 { 500, 0b0100110, 460 }, { 550, 0b0110111, 460 },
125 { 600, 0b0000111, 460 }, { 650, 0b0011000, 460 },
126 { 700, 0b0101000, 460 }, { 750, 0b0111001, 460 },
127 { 800, 0b0001001, 460 }, { 850, 0b0011001, 460 },
128 { 900, 0b0101001, 460 }, { 950, 0b0111010, 460 },
129 { 1000, 0b0001010, 460 }, { 1050, 0b0011010, 460 },
130 { 1110, 0b0101010, 460 }, { 1150, 0b0111011, 460 },
131 { 1200, 0b0001011, 460 }, { 1250, 0b0011011, 460 },
132 { 1300, 0b0101011, 460 }, { 1350, 0b0111100, 460 },
133 { 1400, 0b0001100, 460 }, { 1450, 0b0011100, 460 },
134 { 1500, 0b0101100, 460 }, { 1550, 0b0111101, 285 },
135 { 1600, 0b0001101, 295 }, { 1650, 0b0011101, 304 },
136 { 1700, 0b0101110, 313 }, { 1750, 0b0111110, 322 },
137 { 1800, 0b0001110, 331 }, { 1850, 0b0011110, 341 },
138 { 1900, 0b0101111, 350 }, { 1950, 0b0111111, 359 },
139 { 2000, 0b0001111, 368 }, { 2050, 0b1000000, 377 },
140 { 2100, 0b1000001, 387 }, { 2150, 0b1000010, 396 },
141 { 2200, 0b1000011, 405 }, { 2250, 0b1000100, 414 },
142 { 2300, 0b1000101, 423 }, { 2350, 0b1000110, 432 },
143 { 2400, 0b1000111, 442 }, { 2450, 0b1001000, 451 },
144 { 2500, 0b1001001, 460 }
145 };
146
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-11 7:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 2:42 [PATCH v2 0/2] Synopsys DW DPHY Driver Karthik Poduval
2025-07-10 2:42 ` [PATCH v2 1/2] phy: dw-dphy-rx: Add Synopsys DesignWare D-PHY RX Karthik Poduval
2025-07-10 4:08 ` Frank Li
2025-07-10 5:12 ` Poduval, Karthik
2025-07-10 19:48 ` Frank Li
2025-07-10 4:14 ` Frank Li
2025-07-10 5:15 ` Poduval, Karthik
2025-07-10 7:26 ` Krzysztof Kozlowski
2025-07-10 22:13 ` kernel test robot
2025-07-11 7:13 ` kernel test robot [this message]
2025-07-10 2:42 ` [PATCH v2 2/2] phy: dw-dphy-rx: Add dt bindings for Synopsys MIPI " Karthik Poduval
2025-07-10 3:32 ` Rob Herring (Arm)
2025-07-10 4:02 ` Frank Li
2025-07-10 7:24 ` Krzysztof Kozlowski
2025-07-10 21:24 ` Poduval, Karthik
2025-07-11 7:09 ` Krzysztof Kozlowski
2025-07-10 7:27 ` Krzysztof Kozlowski
2025-07-10 3:56 ` [PATCH v2 0/2] Synopsys DW DPHY Driver Frank Li
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=202507111412.83Oiz7hO-lkp@intel.com \
--to=lkp@intel.com \
--cc=anishkmr@amazon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jyxiong@amazon.com \
--cc=kishon@kernel.org \
--cc=kpoduval@lab126.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=miguel.lopes@synopsys.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--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®