From: kernel test robot <lkp@intel.com>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [rmk-arm:clearfog 80/94] drivers/net/ethernet/marvell/mvgmac.c:174:55: error: 'MVNETA_GMAC_LINK_UP' undeclared; did you mean 'MVGMAC_LINK_UP'?
Date: Tue, 12 Mar 2024 19:00:11 +0800 [thread overview]
Message-ID: <202403121819.ExhV387x-lkp@intel.com> (raw)
tree: git://git.armlinux.org.uk/~rmk/linux-arm clearfog
head: 9d1640e5aae3e685888788662bb7b33adb457f13
commit: 4e45e1b969facc484006a6998cd4d3daadca4fe2 [80/94] net: mvneta: split out GMAC
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240312/202403121819.ExhV387x-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240312/202403121819.ExhV387x-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/202403121819.ExhV387x-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/ethernet/marvell/mvgmac.c: In function 'mvgmac_link_change':
>> drivers/net/ethernet/marvell/mvgmac.c:174:55: error: 'MVNETA_GMAC_LINK_UP' undeclared (first use in this function); did you mean 'MVGMAC_LINK_UP'?
174 | phylink_pcs_change(&gmac->pcs, !!(gmac_stat & MVNETA_GMAC_LINK_UP));
| ^~~~~~~~~~~~~~~~~~~
| MVGMAC_LINK_UP
drivers/net/ethernet/marvell/mvgmac.c:174:55: note: each undeclared identifier is reported only once for each function it appears in
vim +174 drivers/net/ethernet/marvell/mvgmac.c
169
170 void mvgmac_link_change(struct mvgmac *gmac)
171 {
172 u32 gmac_stat = readl_relaxed(gmac->base + GMAC_STATUS_REG);
173
> 174 phylink_pcs_change(&gmac->pcs, !!(gmac_stat & MVNETA_GMAC_LINK_UP));
175 }
176 EXPORT_SYMBOL_GPL(mvgmac_link_change);
177
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-12 11:00 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=202403121819.ExhV387x-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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.