From: kernel test robot <lkp@intel.com>
To: John Ousterhout <ouster@cs.stanford.edu>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
John Ousterhout <ouster@cs.stanford.edu>
Subject: Re: [PATCH net-next v17 14/14] net: homa: create Makefile and Kconfig
Date: Wed, 18 Mar 2026 02:51:02 +0800 [thread overview]
Message-ID: <202603180241.OVIQpOJ1-lkp@intel.com> (raw)
In-Reply-To: <20260316223228.2611-15-ouster@cs.stanford.edu>
Hi John,
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/John-Ousterhout/net-homa-define-user-visible-API-for-Homa/20260317-070659
base: net-next/main
patch link: https://lore.kernel.org/r/20260316223228.2611-15-ouster%40cs.stanford.edu
patch subject: [PATCH net-next v17 14/14] net: homa: create Makefile and Kconfig
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260318/202603180241.OVIQpOJ1-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260318/202603180241.OVIQpOJ1-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/202603180241.OVIQpOJ1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/homa/homa_plumbing.c:94:30: error: initialization of 'int (*)(struct sock *, struct msghdr *, size_t, int)' {aka 'int (*)(struct sock *, struct msghdr *, unsigned int, int)'} from incompatible pointer type 'int (*)(struct sock *, struct msghdr *, size_t, int, int *)' {aka 'int (*)(struct sock *, struct msghdr *, unsigned int, int, int *)'} [-Wincompatible-pointer-types]
94 | .recvmsg = homa_recvmsg,
| ^~~~~~~~~~~~
net/homa/homa_plumbing.c:94:30: note: (near initialization for 'homa_prot.recvmsg')
In file included from net/homa/homa_plumbing.c:7:
net/homa/homa_impl.h:402:10: note: 'homa_recvmsg' declared here
402 | int homa_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
| ^~~~~~~~~~~~
net/homa/homa_plumbing.c:111:30: error: initialization of 'int (*)(struct sock *, struct msghdr *, size_t, int)' {aka 'int (*)(struct sock *, struct msghdr *, unsigned int, int)'} from incompatible pointer type 'int (*)(struct sock *, struct msghdr *, size_t, int, int *)' {aka 'int (*)(struct sock *, struct msghdr *, unsigned int, int, int *)'} [-Wincompatible-pointer-types]
111 | .recvmsg = homa_recvmsg,
| ^~~~~~~~~~~~
net/homa/homa_plumbing.c:111:30: note: (near initialization for 'homav6_prot.recvmsg')
net/homa/homa_impl.h:402:10: note: 'homa_recvmsg' declared here
402 | int homa_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
| ^~~~~~~~~~~~
vim +94 net/homa/homa_plumbing.c
fda29e883f7618 John Ousterhout 2026-03-16 77
fda29e883f7618 John Ousterhout 2026-03-16 78 /* This structure also defines functions that handle various operations
fda29e883f7618 John Ousterhout 2026-03-16 79 * on Homa sockets. However, these functions are lower-level than those
fda29e883f7618 John Ousterhout 2026-03-16 80 * in homa_proto_ops: they are specific to the PF_INET or PF_INET6
fda29e883f7618 John Ousterhout 2026-03-16 81 * protocol family, and in many cases they are invoked by functions in
fda29e883f7618 John Ousterhout 2026-03-16 82 * homa_proto_ops. Most of these functions have Homa-specific implementations.
fda29e883f7618 John Ousterhout 2026-03-16 83 */
fda29e883f7618 John Ousterhout 2026-03-16 84 static struct proto homa_prot = {
fda29e883f7618 John Ousterhout 2026-03-16 85 .name = "HOMA",
fda29e883f7618 John Ousterhout 2026-03-16 86 .owner = THIS_MODULE,
fda29e883f7618 John Ousterhout 2026-03-16 87 .close = homa_close,
fda29e883f7618 John Ousterhout 2026-03-16 88 .connect = ip4_datagram_connect,
fda29e883f7618 John Ousterhout 2026-03-16 89 .init = homa_socket,
fda29e883f7618 John Ousterhout 2026-03-16 90 .destroy = homa_sock_destroy,
fda29e883f7618 John Ousterhout 2026-03-16 91 .setsockopt = homa_setsockopt,
fda29e883f7618 John Ousterhout 2026-03-16 92 .getsockopt = homa_getsockopt,
fda29e883f7618 John Ousterhout 2026-03-16 93 .sendmsg = homa_sendmsg,
fda29e883f7618 John Ousterhout 2026-03-16 @94 .recvmsg = homa_recvmsg,
fda29e883f7618 John Ousterhout 2026-03-16 95 .hash = homa_hash,
fda29e883f7618 John Ousterhout 2026-03-16 96 .unhash = homa_unhash,
fda29e883f7618 John Ousterhout 2026-03-16 97 .obj_size = sizeof(struct homa_sock),
fda29e883f7618 John Ousterhout 2026-03-16 98 .no_autobind = 1,
fda29e883f7618 John Ousterhout 2026-03-16 99 };
fda29e883f7618 John Ousterhout 2026-03-16 100
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-17 18:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 22:32 [PATCH net-next v17 00/14] Begin upstreaming Homa transport protocol John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 01/14] net: homa: define user-visible API for Homa John Ousterhout
2026-03-17 10:10 ` kernel test robot
2026-03-17 18:40 ` kernel test robot
2026-03-16 22:32 ` [PATCH net-next v17 02/14] net: homa: create homa_wire.h John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 03/14] net: homa: create shared Homa header files John Ousterhout
2026-03-18 7:20 ` [net-next,v17,03/14] " Paolo Abeni
2026-03-19 20:37 ` John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 04/14] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 05/14] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,05/14] " Paolo Abeni
2026-03-20 17:13 ` John Ousterhout
2026-03-20 17:20 ` Paolo Abeni
2026-03-16 22:32 ` [PATCH net-next v17 06/14] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 07/14] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,07/14] " Paolo Abeni
2026-03-16 22:32 ` [PATCH net-next v17 08/14] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,08/14] " Paolo Abeni
2026-03-23 22:43 ` John Ousterhout
2026-03-24 8:55 ` Paolo Abeni
2026-03-16 22:32 ` [PATCH net-next v17 09/14] net: homa: create homa_outgoing.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,09/14] " Paolo Abeni
2026-03-20 18:21 ` John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 10/14] net: homa: create homa_utils.c John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 11/14] net: homa: create homa_incoming.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,11/14] " Paolo Abeni
2026-03-20 20:51 ` John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 12/14] net: homa: create homa_timer.c John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 13/14] net: homa: create homa_plumbing.c John Ousterhout
2026-03-18 7:21 ` [net-next,v17,13/14] " Paolo Abeni
2026-03-20 21:49 ` John Ousterhout
2026-03-16 22:32 ` [PATCH net-next v17 14/14] net: homa: create Makefile and Kconfig John Ousterhout
2026-03-17 18:51 ` kernel test robot [this message]
2026-03-17 19:26 ` 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=202603180241.OVIQpOJ1-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ouster@cs.stanford.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox