All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stanislav Fomichev <sdf@fomichev.me>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v2 4/8] net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/
Date: Wed, 2 Jul 2025 14:54:22 +0800	[thread overview]
Message-ID: <202507021431.lqWTrQAr-lkp@intel.com> (raw)
In-Reply-To: <20250630164222.712558-5-sdf@fomichev.me>

Hi Stanislav,

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/Stanislav-Fomichev/net-s-dev_get_stats-netif_get_stats/20250701-004408
base:   net-next/main
patch link:    https://lore.kernel.org/r/20250630164222.712558-5-sdf%40fomichev.me
patch subject: [PATCH net-next v2 4/8] net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/
config: microblaze-defconfig (https://download.01.org/0day-ci/archive/20250702/202507021431.lqWTrQAr-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250702/202507021431.lqWTrQAr-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/202507021431.lqWTrQAr-lkp@intel.com/

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

>> ERROR: modpost: module bridge uses symbol netif_pre_changeaddr_notify from namespace NETDEV_INTERNAL, but does not import it.

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

  reply	other threads:[~2025-07-02  6:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 16:42 [PATCH net-next v2 0/8] net: maintain netif vs dev prefix semantics Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 1/8] net: s/dev_get_stats/netif_get_stats/ Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 2/8] net: s/dev_get_port_parent_id/netif_get_port_parent_id/ Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 3/8] net: s/dev_get_mac_address/netif_get_mac_address/ Stanislav Fomichev
2025-06-30 21:00   ` Willem de Bruijn
2025-06-30 23:19     ` Stanislav Fomichev
2025-07-01 18:59       ` Willem de Bruijn
2025-07-02 15:33         ` Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 4/8] net: s/dev_pre_changeaddr_notify/netif_pre_changeaddr_notify/ Stanislav Fomichev
2025-07-02  6:54   ` kernel test robot [this message]
2025-07-02 22:21   ` kernel test robot
2025-06-30 16:42 ` [PATCH net-next v2 5/8] net: s/__dev_set_mtu/__netif_set_mtu/ Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 6/8] net: s/dev_get_flags/netif_get_flags/ Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 7/8] net: s/dev_set_threaded/netif_set_threaded/ Stanislav Fomichev
2025-06-30 16:42 ` [PATCH net-next v2 8/8] net: s/dev_close_many/netif_close_many/ Stanislav Fomichev

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=202507021431.lqWTrQAr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    /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.