netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>,
	netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andrey.bokhanko@huawei.com,
	Dmitry Skorodumov <skorodumov.dmitry@huawei.com>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>
Subject: Re: [PATCH net-next 01/14] ipvlan: Preparation to support mac-nat
Date: Fri, 7 Nov 2025 07:30:54 +0800	[thread overview]
Message-ID: <202511070917.SA9qQyy5-lkp@intel.com> (raw)
In-Reply-To: <20251105161450.1730216-2-skorodumov.dmitry@huawei.com>

Hi Dmitry,

kernel test robot noticed the following build warnings:

[auto build test WARNING on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Dmitry-Skorodumov/ipvlan-Preparation-to-support-mac-nat/20251106-004449
base:   net-next/main
patch link:    https://lore.kernel.org/r/20251105161450.1730216-2-skorodumov.dmitry%40huawei.com
patch subject: [PATCH net-next 01/14] ipvlan: Preparation to support mac-nat
config: s390-randconfig-001-20251107 (https://download.01.org/0day-ci/archive/20251107/202511070917.SA9qQyy5-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251107/202511070917.SA9qQyy5-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/202511070917.SA9qQyy5-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/net/ipvlan/ipvlan_core.c:435:13: warning: 'is_ipv6_usable' defined but not used [-Wunused-function]
    static bool is_ipv6_usable(const struct in6_addr *addr)
                ^~~~~~~~~~~~~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for OF_GPIO
   Depends on [n]: GPIOLIB [=y] && OF [=y] && HAS_IOMEM [=n]
   Selected by [m]:
   - REGULATOR_RT5133 [=m] && REGULATOR [=y] && I2C [=m] && GPIOLIB [=y] && OF [=y]


vim +/is_ipv6_usable +435 drivers/net/ipvlan/ipvlan_core.c

   434	
 > 435	static bool is_ipv6_usable(const struct in6_addr *addr)
   436	{
   437		return !ipv6_addr_is_multicast(addr) && !ipv6_addr_loopback(addr) &&
   438		       !ipv6_addr_any(addr);
   439	}
   440	

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

  parent reply	other threads:[~2025-11-06 23:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 16:14 [PATCH net-next v3 00/14] ipvlan: support mac-nat mode Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 01/14] ipvlan: Preparation to support mac-nat Dmitry Skorodumov
2025-11-05 23:32   ` Bagas Sanjaya
2025-11-06 23:30   ` kernel test robot [this message]
2025-11-05 16:14 ` [PATCH net-next 02/14] ipvlan: Send mcasts out directly in ipvlan_xmit_mode_l2() Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 03/14] ipvlan: Handle rx mcast-ip and unicast eth Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 04/14] ipvlan: Added some kind of MAC NAT Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 05/14] ipvlan: Forget all IP when device goes down Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 06/14] ipvlan: Support GSO for port -> ipvlan Dmitry Skorodumov
2025-11-05 16:29   ` Eric Dumazet
2025-11-05 16:58     ` Dmitry Skorodumov
2025-11-06 15:41       ` Dmitry Skorodumov
2025-11-06 15:56         ` Eric Dumazet
2025-11-07 11:26           ` Dmitry Skorodumov
2025-11-06 16:19         ` Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 07/14] ipvlan: Support IPv6 for learnable l2-bridge Dmitry Skorodumov
2025-11-11  0:33   ` kernel test robot
2025-11-05 16:14 ` [PATCH net-next 08/14] ipvlan: Make the addrs_lock be per port Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 09/14] ipvlan: Take addr_lock in ipvlan_open() Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 10/14] ipvlan: Don't allow children to use IPs of main Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 11/14] ipvlan: const-specifier for functions that use iaddr Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 12/14] ipvlan: Common code from v6/v4 validator_event Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 13/14] ipvlan: common code to handle ipv6/ipv4 address events Dmitry Skorodumov
2025-11-05 16:14 ` [PATCH net-next 14/14] ipvlan: Ignore PACKET_LOOPBACK in handle_mode_l2() Dmitry Skorodumov
2025-11-06  9:03 ` [syzbot ci] Re: ipvlan: support mac-nat mode syzbot ci
  -- strict thread matches above, loose matches on Subject: below --
2025-11-05 16:07 [PATCH net-next v2 00/14] " Dmitry Skorodumov
2025-11-05 16:07 ` [PATCH net-next 01/14] ipvlan: Preparation to support mac-nat Dmitry Skorodumov

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=202511070917.SA9qQyy5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrey.bokhanko@huawei.com \
    --cc=corbet@lwn.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=skorodumov.dmitry@huawei.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).