From: kernel test robot <lkp@intel.com>
To: Stefan Wahren <wahrenst@gmx.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
devicetree@vger.kernel.org, Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH net-next 2/5] net: vertexcom: mse102x: Add warning about IRQ trigger type
Date: Thu, 8 May 2025 17:00:04 +0800 [thread overview]
Message-ID: <202505081612.wbRgFMC7-lkp@intel.com> (raw)
In-Reply-To: <20250505142427.9601-3-wahrenst@gmx.net>
Hi Stefan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Stefan-Wahren/dt-bindings-vertexcom-mse102x-Fix-IRQ-type-in-example/20250505-222628
base: net-next/main
patch link: https://lore.kernel.org/r/20250505142427.9601-3-wahrenst%40gmx.net
patch subject: [PATCH net-next 2/5] net: vertexcom: mse102x: Add warning about IRQ trigger type
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20250508/202505081612.wbRgFMC7-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505081612.wbRgFMC7-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/202505081612.wbRgFMC7-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/vertexcom/mse102x.c: In function 'mse102x_net_open':
drivers/net/ethernet/vertexcom/mse102x.c:525:37: error: implicit declaration of function 'irq_get_irq_data'; did you mean 'irq_set_irq_wake'? [-Werror=implicit-function-declaration]
525 | struct irq_data *irq_data = irq_get_irq_data(ndev->irq);
| ^~~~~~~~~~~~~~~~
| irq_set_irq_wake
>> drivers/net/ethernet/vertexcom/mse102x.c:525:37: warning: initialization of 'struct irq_data *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
drivers/net/ethernet/vertexcom/mse102x.c:535:17: error: implicit declaration of function 'irqd_get_trigger_type'; did you mean 'led_get_trigger_data'? [-Werror=implicit-function-declaration]
535 | switch (irqd_get_trigger_type(irq_data)) {
| ^~~~~~~~~~~~~~~~~~~~~
| led_get_trigger_data
drivers/net/ethernet/vertexcom/mse102x.c:536:14: error: 'IRQ_TYPE_LEVEL_HIGH' undeclared (first use in this function)
536 | case IRQ_TYPE_LEVEL_HIGH:
| ^~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/vertexcom/mse102x.c:536:14: note: each undeclared identifier is reported only once for each function it appears in
drivers/net/ethernet/vertexcom/mse102x.c:537:14: error: 'IRQ_TYPE_LEVEL_LOW' undeclared (first use in this function)
537 | case IRQ_TYPE_LEVEL_LOW:
| ^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +525 drivers/net/ethernet/vertexcom/mse102x.c
522
523 static int mse102x_net_open(struct net_device *ndev)
524 {
> 525 struct irq_data *irq_data = irq_get_irq_data(ndev->irq);
526 struct mse102x_net *mse = netdev_priv(ndev);
527 struct mse102x_net_spi *mses = to_mse102x_spi(mse);
528 int ret;
529
530 if (!irq_data) {
531 netdev_err(ndev, "Invalid IRQ: %d\n", ndev->irq);
532 return -EINVAL;
533 }
534
535 switch (irqd_get_trigger_type(irq_data)) {
536 case IRQ_TYPE_LEVEL_HIGH:
537 case IRQ_TYPE_LEVEL_LOW:
538 break;
539 default:
540 netdev_warn_once(ndev, "Only IRQ type level recommended, please update your firmware.\n");
541 break;
542 }
543
544 ret = request_threaded_irq(ndev->irq, NULL, mse102x_irq, IRQF_ONESHOT,
545 ndev->name, mse);
546 if (ret < 0) {
547 netdev_err(ndev, "Failed to get irq: %d\n", ret);
548 return ret;
549 }
550
551 netif_dbg(mse, ifup, ndev, "opening\n");
552
553 netif_start_queue(ndev);
554
555 netif_carrier_on(ndev);
556
557 /* The SPI interrupt can stuck in case of pending packet(s).
558 * So poll for possible packet(s) to re-arm the interrupt.
559 */
560 mutex_lock(&mses->lock);
561 mse102x_rx_pkt_spi(mse);
562 mutex_unlock(&mses->lock);
563
564 netif_dbg(mse, ifup, ndev, "network device up\n");
565
566 return 0;
567 }
568
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-08 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 14:24 [PATCH net-next 0/5] net: vertexcom: mse102x: Improve RX handling Stefan Wahren
2025-05-05 14:24 ` [PATCH net-next 1/5] dt-bindings: vertexcom-mse102x: Fix IRQ type in example Stefan Wahren
2025-05-05 16:31 ` Andrew Lunn
2025-05-05 14:24 ` [PATCH net-next 2/5] net: vertexcom: mse102x: Add warning about IRQ trigger type Stefan Wahren
2025-05-05 16:32 ` Andrew Lunn
2025-05-06 8:38 ` Stefan Wahren
2025-05-06 12:24 ` Andrew Lunn
2025-05-05 20:57 ` Jakub Kicinski
2025-05-07 10:25 ` kernel test robot
2025-05-07 14:35 ` Stefan Wahren
2025-05-08 9:00 ` kernel test robot [this message]
2025-05-05 14:24 ` [PATCH net-next 3/5] net: vertexcom: mse102x: Drop invalid cmd stats Stefan Wahren
2025-05-05 16:35 ` Andrew Lunn
2025-05-05 17:28 ` Stefan Wahren
2025-05-05 14:24 ` [PATCH net-next 4/5] net: vertexcom: mse102x: Return code for mse102x_rx_pkt_spi Stefan Wahren
2025-05-05 16:43 ` Andrew Lunn
2025-05-05 17:16 ` Stefan Wahren
2025-05-05 19:27 ` Andrew Lunn
2025-05-06 8:24 ` Stefan Wahren
2025-05-05 14:24 ` [PATCH net-next 5/5] net: vertexcom: mse102x: Simplify mse102x_rx_pkt_spi Stefan Wahren
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=202505081612.wbRgFMC7-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=wahrenst@gmx.net \
/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).