From: kernel test robot <lkp@intel.com>
To: Tomer Maimon <tmaimon77@gmail.com>,
davem@davemloft.net, edumazet@google.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, alexandre.torgue@foss.st.com,
peppe.cavallaro@st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, avifishman70@gmail.com,
tali.perry1@gmail.com, joel@jms.id.au,
andrew@codeconstruct.com.au, venture@google.com,
yuenn@google.com, benjaminfair@google.com, j.neuschaefer@gmx.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
openbmc@lists.ozlabs.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Tomer Maimon <tmaimon77@gmail.com>
Subject: Re: [PATCH v1 2/2] net: stmmac: Add NPCM support
Date: Wed, 22 Nov 2023 10:11:01 +0800 [thread overview]
Message-ID: <202311221011.bsAmeQ6v-lkp@intel.com> (raw)
In-Reply-To: <20231121151733.2015384-3-tmaimon77@gmail.com>
Hi Tomer,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on net-next/main net/main linus/master v6.7-rc2 next-20231121]
[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/Tomer-Maimon/dt-bindings-net-Add-support-NPCM-dwmac/20231121-231908
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20231121151733.2015384-3-tmaimon77%40gmail.com
patch subject: [PATCH v1 2/2] net: stmmac: Add NPCM support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20231122/202311221011.bsAmeQ6v-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231122/202311221011.bsAmeQ6v-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/202311221011.bsAmeQ6v-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/stmicro/stmmac/dwmac-npcm.c:53:6: warning: no previous prototype for function 'npcm_dwmac_pcs_init' [-Wmissing-prototypes]
void npcm_dwmac_pcs_init(struct npcm_dwmac *dwmac, struct device *dev,
^
drivers/net/ethernet/stmicro/stmmac/dwmac-npcm.c:53:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void npcm_dwmac_pcs_init(struct npcm_dwmac *dwmac, struct device *dev,
^
static
1 warning generated.
vim +/npcm_dwmac_pcs_init +53 drivers/net/ethernet/stmicro/stmmac/dwmac-npcm.c
52
> 53 void npcm_dwmac_pcs_init(struct npcm_dwmac *dwmac, struct device *dev,
54 struct plat_stmmacenet_data *plat_dat)
55 {
56 u16 val;
57
58 iowrite16((u16)(SR_MII_CTRL >> 9), dwmac->reg + IND_AC_BA_REG);
59 val = ioread16(dwmac->reg + PCS_SR_MII_CTRL_REG);
60 val |= PCS_RST;
61 iowrite16(val, dwmac->reg + PCS_SR_MII_CTRL_REG);
62
63 while (val & PCS_RST)
64 val = ioread16(dwmac->reg + PCS_SR_MII_CTRL_REG);
65
66 val &= ~(PCS_AN_ENABLE);
67 iowrite16(val, dwmac->reg + PCS_SR_MII_CTRL_REG);
68 }
69
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-22 2:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 15:17 [PATCH v1 0/2] net: stmmac: add NPCM dwmac support Tomer Maimon
2023-11-21 15:17 ` [PATCH v1 1/2] dt-bindings: net: Add support NPCM dwmac Tomer Maimon
2023-11-21 17:21 ` Krzysztof Kozlowski
2023-11-21 15:17 ` [PATCH v1 2/2] net: stmmac: Add NPCM support Tomer Maimon
2023-11-21 15:45 ` Russell King (Oracle)
2023-11-22 17:23 ` Tomer Maimon
2023-11-27 15:58 ` Russell King (Oracle)
2023-11-30 17:15 ` Tomer Maimon
2023-11-21 16:00 ` Andrew Lunn
2023-11-22 17:50 ` Tomer Maimon
2023-11-22 18:45 ` Andrew Lunn
2023-11-23 13:50 ` Tomer Maimon
2023-11-27 15:19 ` Tomer Maimon
2023-11-28 23:31 ` Andrew Lunn
2023-11-30 17:17 ` Tomer Maimon
2023-11-30 17:26 ` Andrew Lunn
2023-11-30 18:25 ` Tomer Maimon
2023-11-30 19:59 ` Serge Semin
2023-11-30 20:34 ` [Linux-stm32] " Maxime Chevallier
2023-12-01 16:25 ` Serge Semin
2023-11-22 2:11 ` kernel test robot [this message]
2023-11-22 4:45 ` kernel test robot
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=202311221011.bsAmeQ6v-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=j.neuschaefer@gmx.net \
--cc=joabreu@synopsys.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=llvm@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openbmc@lists.ozlabs.org \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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;
as well as URLs for NNTP newsgroup(s).