From: Simon Horman <horms@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
kuba@kernel.org
Subject: Re: [PATCH net-next v16 01/14] net: homa: define user-visible API for Homa
Date: Mon, 27 Oct 2025 09:37:30 +0000 [thread overview]
Message-ID: <aP89WhbDEzt24sFG@horms.kernel.org> (raw)
In-Reply-To: <20251015185102.2444-2-ouster@cs.stanford.edu>
On Wed, Oct 15, 2025 at 11:50:48AM -0700, John Ousterhout wrote:
> Note: for man pages, see the Homa Wiki at:
> https://homa-transport.atlassian.net/wiki/spaces/HOMA/overview
>
> Signed-off-by: John Ousterhout <ouster@cs.stanford.edu>
...
> diff --git a/net/Kconfig b/net/Kconfig
> index d5865cf19799..92972ff2a78d 100644
> --- a/net/Kconfig
> +++ b/net/Kconfig
> @@ -250,6 +250,7 @@ source "net/bridge/netfilter/Kconfig"
> endif # if NETFILTER
>
> source "net/sctp/Kconfig"
> +source "net/homa/Kconfig"
> source "net/rds/Kconfig"
> source "net/tipc/Kconfig"
> source "net/atm/Kconfig"
Hi John,
I think that the hunk above needs to wait until a patch
that adds net/homa/Kconfig. As is, this breaks builds.
Possibly the same is also true of the hunk below,
but the build didn't get that far.
> diff --git a/net/Makefile b/net/Makefile
> index aac960c41db6..71f740e0dc34 100644
> --- a/net/Makefile
> +++ b/net/Makefile
> @@ -43,6 +43,7 @@ ifneq ($(CONFIG_VLAN_8021Q),)
> obj-y += 8021q/
> endif
> obj-$(CONFIG_IP_SCTP) += sctp/
> +obj-$(CONFIG_HOMA) += homa/
> obj-$(CONFIG_RDS) += rds/
> obj-$(CONFIG_WIRELESS) += wireless/
> obj-$(CONFIG_MAC80211) += mac80211/
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-10-27 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 18:50 [PATCH net-next v16 00/14] Begin upstreaming Homa transport protocol John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 01/14] net: homa: define user-visible API for Homa John Ousterhout
2025-10-27 9:37 ` Simon Horman [this message]
2025-10-27 15:25 ` John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 02/14] net: homa: create homa_wire.h John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 03/14] net: homa: create shared Homa header files John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 04/14] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 05/14] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 06/14] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 07/14] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 08/14] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 09/14] net: homa: create homa_outgoing.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 10/14] net: homa: create homa_utils.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 11/14] net: homa: create homa_incoming.c John Ousterhout
2025-10-15 18:50 ` [PATCH net-next v16 12/14] net: homa: create homa_timer.c John Ousterhout
2025-10-15 18:51 ` [PATCH net-next v16 13/14] net: homa: create homa_plumbing.c John Ousterhout
2025-10-15 18:51 ` [PATCH net-next v16 14/14] net: homa: create Makefile and Kconfig John Ousterhout
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=aP89WhbDEzt24sFG@horms.kernel.org \
--to=horms@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).