From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: kernel test robot <lkp@intel.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH net-next v3 3/3] net: phy: dp83tg720: Add cable testing support
Date: Sat, 10 Aug 2024 19:22:00 +0200 [thread overview]
Message-ID: <52f84b76-3849-4fc7-94a3-fbaf23ce99af@lunn.ch> (raw)
In-Reply-To: <ZrcF0HyEUMSudk5M@pengutronix.de>
On Sat, Aug 10, 2024 at 08:16:48AM +0200, Oleksij Rempel wrote:
> On Sat, Aug 10, 2024 at 03:57:35AM +0800, kernel test robot wrote:
> > Hi Oleksij,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on net-next/main]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Oleksij-Rempel/phy-Add-Open-Alliance-helpers-for-the-PHY-framework/20240809-172119
> > base: net-next/main
> > patch link: https://lore.kernel.org/r/20240809072440.3477125-3-o.rempel%40pengutronix.de
> > patch subject: [PATCH net-next v3 3/3] net: phy: dp83tg720: Add cable testing support
> > config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240810/202408100348.U6S1jP0z-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 14.1.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240810/202408100348.U6S1jP0z-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/202408100348.U6S1jP0z-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/net/phy/open_alliance_helpers.c: In function 'oa_1000bt1_get_ethtool_cable_result_code':
> > >> drivers/net/phy/open_alliance_helpers.c:34:25: error: implicit declaration of function 'FIELD_GET' [-Wimplicit-function-declaration]
> > 34 | u8 tdr_status = FIELD_GET(OA_1000BT1_HDD_TDR_STATUS_MASK, reg_value);
> > | ^~~~~~~~~
>
> Huh.. why it builds on arm?
There has been a couple of reports like this recently. I suspect there
is a some architecture header pulling in the needed header, and m68k
does not.
You might want to compare drivers/net/phy/open_alliance_helpers.i for
arm and m68k.
Andrew
prev parent reply other threads:[~2024-08-10 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 7:24 [PATCH net-next v3 1/3] ethtool: Add new result codes for TDR diagnostics Oleksij Rempel
2024-08-09 7:24 ` [PATCH net-next v3 2/3] phy: Add Open Alliance helpers for the PHY framework Oleksij Rempel
2024-08-09 7:24 ` [PATCH net-next v3 3/3] net: phy: dp83tg720: Add cable testing support Oleksij Rempel
2024-08-09 17:55 ` kernel test robot
2024-08-09 19:57 ` kernel test robot
2024-08-10 6:16 ` Oleksij Rempel
2024-08-10 17:22 ` Andrew Lunn [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=52f84b76-3849-4fc7-94a3-fbaf23ce99af@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®