public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joshua Washington <joshwash@google.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
	Joshua Washington <joshwash@google.com>,
	Harshitha Ramamurthy <hramamurthy@google.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Willem de Bruijn <willemb@google.com>,
	Praveen Kaligineedi <pkaligineedi@google.com>,
	Ziwei Xiao <ziweixiao@google.com>,
	John Fraker <jfraker@google.com>, Matt Olson <maolson@google.com>,
	Bailey Forrest <bcf@google.com>,
	Tim Hostetler <thostet@google.com>,
	Jordan Rhee <jordanrhee@google.com>,
	linux-kernel@vger.kernel.org, Max Yuan <maxyuan@google.com>
Subject: Re: [PATCH net-next 1/2] gve: Update QPL page registration logic
Date: Sat, 14 Feb 2026 05:43:30 +0800	[thread overview]
Message-ID: <202602140501.JzPUyrJP-lkp@intel.com> (raw)
In-Reply-To: <20260207011734.437205-2-joshwash@google.com>

Hi Joshua,

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/Joshua-Washington/gve-Update-QPL-page-registration-logic/20260207-092137
base:   net-next/main
patch link:    https://lore.kernel.org/r/20260207011734.437205-2-joshwash%40google.com
patch subject: [PATCH net-next 1/2] gve: Update QPL page registration logic
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20260214/202602140501.JzPUyrJP-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260214/202602140501.JzPUyrJP-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/202602140501.JzPUyrJP-lkp@intel.com/

All errors (new ones prefixed by >>, old ones prefixed by <<):

>> ERROR: modpost: "__udivdi3" [drivers/net/ethernet/google/gve/gve.ko] undefined!

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-02-13 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07  1:17 [PATCH net-next 0/2] gve: Support larger ring sizes in DQO-QPL mode Joshua Washington
2026-02-07  1:17 ` [PATCH net-next 1/2] gve: Update QPL page registration logic Joshua Washington
2026-02-11  9:34   ` Paolo Abeni
2026-02-13 21:43   ` kernel test robot [this message]
2026-02-07  1:17 ` [PATCH net-next 2/2] gve: Enable reading max ring size from the device in DQO-QPL mode Joshua Washington

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=202602140501.JzPUyrJP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bcf@google.com \
    --cc=edumazet@google.com \
    --cc=hramamurthy@google.com \
    --cc=jfraker@google.com \
    --cc=jordanrhee@google.com \
    --cc=joshwash@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maolson@google.com \
    --cc=maxyuan@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=pkaligineedi@google.com \
    --cc=thostet@google.com \
    --cc=willemb@google.com \
    --cc=ziweixiao@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