From: kernel test robot <lkp@intel.com>
To: David Wilder <wilder@us.ibm.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jv@jvosburgh.net,
wilder@us.ibm.com, pradeeps@linux.vnet.ibm.com,
pradeep@us.ibm.com, i.maximets@ovn.org, amorenoz@redhat.com,
haliu@redhat.com
Subject: Re: [PATCH net-next v3 2/4] bonding: Extend arp_ip_target format to allow for a list of vlan tags.
Date: Sun, 15 Jun 2025 13:42:19 +0800 [thread overview]
Message-ID: <202506151306.ebIcSmWf-lkp@intel.com> (raw)
In-Reply-To: <20250614014900.226472-3-wilder@us.ibm.com>
Hi David,
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/David-Wilder/bonding-Adding-struct-bond_arp_target/20250614-095027
base: net-next/main
patch link: https://lore.kernel.org/r/20250614014900.226472-3-wilder%40us.ibm.com
patch subject: [PATCH net-next v3 2/4] bonding: Extend arp_ip_target format to allow for a list of vlan tags.
config: openrisc-randconfig-r133-20250615 (https://download.01.org/0day-ci/archive/20250615/202506151306.ebIcSmWf-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.1.0
reproduce: (https://download.01.org/0day-ci/archive/20250615/202506151306.ebIcSmWf-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/202506151306.ebIcSmWf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/bonding/bond_options.c:1244:34: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [addressable] [usertype] target_ip @@ got unsigned long long const [usertype] value @@
drivers/net/bonding/bond_options.c:1244:34: sparse: expected restricted __be32 [addressable] [usertype] target_ip
drivers/net/bonding/bond_options.c:1244:34: sparse: got unsigned long long const [usertype] value
drivers/net/bonding/bond_options.c: note: in included file:
>> include/net/bonding.h:810:55: sparse: sparse: Using plain integer as NULL pointer
--
drivers/net/bonding/bond_main.c: note: in included file:
>> include/net/bonding.h:810:55: sparse: sparse: Using plain integer as NULL pointer
vim +1244 drivers/net/bonding/bond_options.c
1224
1225 static int bond_option_arp_ip_targets_set(struct bonding *bond,
1226 const struct bond_opt_value *newval)
1227 {
1228 int ret = -EPERM;
1229 struct bond_arp_target target;
1230
1231 if (newval->string) {
1232 if (strlen(newval->string) < 1 ||
1233 bond_arp_ip_target_opt_parse(newval->string + 1, &target)) {
1234 netdev_err(bond->dev, "invalid ARP target specified\n");
1235 return ret;
1236 }
1237 if (newval->string[0] == '+')
1238 ret = bond_option_arp_ip_target_add(bond, target);
1239 else if (newval->string[0] == '-')
1240 ret = bond_option_arp_ip_target_rem(bond, target);
1241 else
1242 netdev_err(bond->dev, "no command found in arp_ip_targets file - use +<addr> or -<addr>\n");
1243 } else {
> 1244 target.target_ip = newval->value;
1245 ret = bond_option_arp_ip_target_add(bond, target);
1246 }
1247
1248 return ret;
1249 }
1250
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-15 5:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 1:48 [PATCH net-next v3 0/4] bonding: Extend arp_ip_target format to allow for a list of vlan tags David Wilder
2025-06-14 1:48 ` [PATCH net-next v3 1/4] bonding: Adding struct bond_arp_target David Wilder
2025-06-14 1:48 ` [PATCH net-next v3 2/4] bonding: Extend arp_ip_target format to allow for a list of vlan tags David Wilder
2025-06-15 5:42 ` kernel test robot [this message]
2025-06-16 23:15 ` Jay Vosburgh
2025-06-17 15:45 ` David Wilder
2025-06-17 16:06 ` Jay Vosburgh
2025-06-14 1:48 ` [PATCH net-next v3 3/4] bonding: Selftest for the arp_ip_target parameter David Wilder
2025-06-14 1:48 ` [PATCH net-next v3 4/4] bonding: Update to the bonding documentation David Wilder
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=202506151306.ebIcSmWf-lkp@intel.com \
--to=lkp@intel.com \
--cc=amorenoz@redhat.com \
--cc=haliu@redhat.com \
--cc=i.maximets@ovn.org \
--cc=jv@jvosburgh.net \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pradeep@us.ibm.com \
--cc=pradeeps@linux.vnet.ibm.com \
--cc=wilder@us.ibm.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.