mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Philo Lu <lulie@linux.alibaba.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, willemdebruijn.kernel@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, dsahern@kernel.org, horms@kernel.org,
	antony.antony@secunet.com, steffen.klassert@secunet.com,
	linux-kernel@vger.kernel.org, dust.li@linux.alibaba.com,
	jakub@cloudflare.com, fred.cc@alibaba-inc.com,
	yubing.qiuyubing@alibaba-inc.com
Subject: Re: [PATCH v7 net-next 4/4] ipv6/udp: Add 4-tuple hash for connected socket
Date: Wed, 6 Nov 2024 11:29:00 +0800	[thread overview]
Message-ID: <202411061155.g9trZ6rZ-lkp@intel.com> (raw)
In-Reply-To: <20241105121225.12513-5-lulie@linux.alibaba.com>

Hi Philo,

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/Philo-Lu/net-udp-Add-a-new-struct-for-hash2-slot/20241105-201454
base:   net-next/main
patch link:    https://lore.kernel.org/r/20241105121225.12513-5-lulie%40linux.alibaba.com
patch subject: [PATCH v7 net-next 4/4] ipv6/udp: Add 4-tuple hash for connected socket
config: arc-randconfig-002-20241106 (https://download.01.org/0day-ci/archive/20241106/202411061155.g9trZ6rZ-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411061155.g9trZ6rZ-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/202411061155.g9trZ6rZ-lkp@intel.com/

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

>> ERROR: modpost: "udp_lib_hash4" [net/ipv6/ipv6.ko] undefined!
>> ERROR: modpost: "udp_ehashfn" [net/ipv6/ipv6.ko] undefined!
>> ERROR: modpost: "udp4_hash4" [net/ipv6/ipv6.ko] undefined!

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

      parent reply	other threads:[~2024-11-06  3:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 12:12 [PATCH v7 net-next 0/4] udp: Add 4-tuple hash for connected sockets Philo Lu
2024-11-05 12:12 ` [PATCH v7 net-next 1/4] net/udp: Add a new struct for hash2 slot Philo Lu
2024-11-05 12:12 ` [PATCH v7 net-next 2/4] net/udp: Add 4-tuple hash list basis Philo Lu
2024-11-05 12:12 ` [PATCH v7 net-next 3/4] ipv4/udp: Add 4-tuple hash for connected socket Philo Lu
2024-11-05 12:12 ` [PATCH v7 net-next 4/4] ipv6/udp: " Philo Lu
2024-11-06  1:53   ` Philo Lu
2024-11-06  3:29   ` kernel test robot [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=202411061155.g9trZ6rZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=antony.antony@secunet.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=fred.cc@alibaba-inc.com \
    --cc=horms@kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lulie@linux.alibaba.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=yubing.qiuyubing@alibaba-inc.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®