netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
	Willem de Bruijn <willemb@google.com>,
	Simon Horman <horms@kernel.org>,
	eric.dumazet@gmail.com, Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 3/4] tcp: use EXPORT_IPV6_MOD[_GPL]()
Date: Mon, 10 Feb 2025 20:21:22 +0800	[thread overview]
Message-ID: <202502102052.AL2TIjxx-lkp@intel.com> (raw)
In-Reply-To: <20250210082805.465241-4-edumazet@google.com>

Hi Eric,

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/Eric-Dumazet/net-introduce-EXPORT_IPV6_MOD-and-EXPORT_IPV6_MOD_GPL/20250210-163000
base:   net-next/main
patch link:    https://lore.kernel.org/r/20250210082805.465241-4-edumazet%40google.com
patch subject: [PATCH net-next 3/4] tcp: use EXPORT_IPV6_MOD[_GPL]()
config: i386-buildonly-randconfig-002-20250210 (https://download.01.org/0day-ci/archive/20250210/202502102052.AL2TIjxx-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/20250210/202502102052.AL2TIjxx-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/202502102052.AL2TIjxx-lkp@intel.com/

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

WARNING: modpost: missing MODULE_DESCRIPTION() in fs/exportfs/exportfs.o
>> ERROR: modpost: "tcp_memory_pressure" [net/tls/tls.ko] undefined!
>> ERROR: modpost: "tcp_poll" [net/tls/tls.ko] undefined!

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

  parent reply	other threads:[~2025-02-10 12:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  8:28 [PATCH net-next 0/4] net: add EXPORT_IPV6_MOD() Eric Dumazet
2025-02-10  8:28 ` [PATCH net-next 1/4] net: introduce EXPORT_IPV6_MOD() and EXPORT_IPV6_MOD_GPL() Eric Dumazet
2025-02-10  8:28 ` [PATCH net-next 2/4] inetpeer: use EXPORT_IPV6_MOD[_GPL]() Eric Dumazet
2025-02-10  8:28 ` [PATCH net-next 3/4] tcp: " Eric Dumazet
2025-02-10  8:41   ` Mateusz Polchlopek
2025-02-10  9:08     ` Eric Dumazet
2025-02-10  9:23       ` Mateusz Polchlopek
2025-02-10  9:30   ` Sabrina Dubroca
2025-02-10  9:44     ` Eric Dumazet
2025-02-10  9:56       ` Eric Dumazet
2025-02-10 11:35         ` Sabrina Dubroca
2025-02-10 12:26           ` Eric Dumazet
2025-02-10 12:21   ` kernel test robot [this message]
2025-02-10  8:28 ` [PATCH net-next 4/4] udp: " Eric Dumazet
2025-02-11  2:56   ` Willem de Bruijn
2025-02-11  8:08     ` Eric Dumazet
2025-02-10  9:25 ` [PATCH net-next 0/4] net: add EXPORT_IPV6_MOD() Mateusz Polchlopek
2025-02-10 18:33 ` Willem de Bruijn
2025-02-10 18:46   ` Eric Dumazet

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=202502102052.AL2TIjxx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=willemb@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;
as well as URLs for NNTP newsgroup(s).