From: kernel test robot <lkp@intel.com>
To: Fernando Fernandez Mancera <fmancera@suse.de>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, horms@kernel.org,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
dsahern@kernel.org, davem@davemloft.net,
Fernando Fernandez Mancera <fmancera@suse.de>
Subject: Re: [PATCH 2/2 net-next] ipv4: ipv4: handle devconf post-set actions on netlink updates
Date: Thu, 26 Mar 2026 15:25:37 +0800 [thread overview]
Message-ID: <202603261543.ZsP9A5JB-lkp@intel.com> (raw)
In-Reply-To: <20260325161020.3516-2-fmancera@suse.de>
Hi Fernando,
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/Fernando-Fernandez-Mancera/ipv4-ipv4-handle-devconf-post-set-actions-on-netlink-updates/20260326-020953
base: net-next/main
patch link: https://lore.kernel.org/r/20260325161020.3516-2-fmancera%40suse.de
patch subject: [PATCH 2/2 net-next] ipv4: ipv4: handle devconf post-set actions on netlink updates
config: um-randconfig-002-20260326 (https://download.01.org/0day-ci/archive/20260326/202603261543.ZsP9A5JB-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/20260326/202603261543.ZsP9A5JB-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/202603261543.ZsP9A5JB-lkp@intel.com/
All errors (new ones prefixed by >>):
/usr/bin/ld: net/ipv4/devinet.o: in function `inet_set_link_af':
>> devinet.c:(.text+0x117d): undefined reference to `devinet_conf_post_set'
collect2: error: ld returned 1 exit status
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-26 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 16:10 [PATCH 1/2 net-next] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-03-25 16:10 ` [PATCH 2/2 net-next] ipv4: ipv4: handle devconf post-set actions on netlink updates Fernando Fernandez Mancera
2026-03-25 20:39 ` Fernando Fernandez Mancera
2026-03-26 3:39 ` kernel test robot
2026-03-26 7:25 ` kernel test robot [this message]
2026-03-26 12:08 ` kernel test robot
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=202603261543.ZsP9A5JB-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.