netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	robh@kernel.org, johannes@sipsolutions.net,
	stephen@networkplumber.org, ecree.xilinx@gmail.com,
	sdf@google.com, f.fainelli@gmail.com, fw@strlen.de,
	linux-doc@vger.kernel.org, razor@blackwall.org,
	nicolas.dichtel@6wind.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v4 6/8] net: fou: rename the source for linking
Date: Fri, 20 Jan 2023 09:50:39 -0800	[thread overview]
Message-ID: <20230120175041.342573-7-kuba@kernel.org> (raw)
In-Reply-To: <20230120175041.342573-1-kuba@kernel.org>

We'll need to link two objects together to form the fou module.
This means the source can't be called fou, the build system expects
fou.o to be the combined object.

Acked-by: Stanislav Fomichev <sdf@google.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
 net/ipv4/Makefile              | 1 +
 net/ipv4/{fou.c => fou_core.c} | 0
 2 files changed, 1 insertion(+)
 rename net/ipv4/{fou.c => fou_core.c} (100%)

diff --git a/net/ipv4/Makefile b/net/ipv4/Makefile
index af7d2cf490fb..fabbe46897ce 100644
--- a/net/ipv4/Makefile
+++ b/net/ipv4/Makefile
@@ -26,6 +26,7 @@ obj-$(CONFIG_IP_MROUTE) += ipmr.o
 obj-$(CONFIG_IP_MROUTE_COMMON) += ipmr_base.o
 obj-$(CONFIG_NET_IPIP) += ipip.o
 gre-y := gre_demux.o
+fou-y := fou_core.o
 obj-$(CONFIG_NET_FOU) += fou.o
 obj-$(CONFIG_NET_IPGRE_DEMUX) += gre.o
 obj-$(CONFIG_NET_IPGRE) += ip_gre.o
diff --git a/net/ipv4/fou.c b/net/ipv4/fou_core.c
similarity index 100%
rename from net/ipv4/fou.c
rename to net/ipv4/fou_core.c
-- 
2.39.0


  parent reply	other threads:[~2023-01-20 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 17:50 [PATCH net-next v4 0/8] Netlink protocol specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 1/8] docs: add more netlink docs (incl. spec docs) Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 2/8] netlink: add schemas for YAML specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 3/8] net: add basic C code generators for Netlink Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 4/8] netlink: add a proto specification for FOU Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 5/8] net: fou: regenerate the uAPI from the spec Jakub Kicinski
2023-01-24 17:49   ` Alexander Lobakin
2023-01-24 18:50     ` Johannes Berg
2023-01-25  0:40       ` Jakub Kicinski
2023-01-25 10:16         ` Alexander Lobakin
2023-01-20 17:50 ` Jakub Kicinski [this message]
2023-01-20 17:50 ` [PATCH net-next v4 7/8] net: fou: use policy and operation tables generated " Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 8/8] tools: ynl: add a completely generic client Jakub Kicinski
2023-01-24 10:29 ` [PATCH net-next v4 0/8] Netlink protocol specs Paolo Abeni
2023-01-24 10:40 ` patchwork-bot+netdevbpf

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=20230120175041.342573-7-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=robh@kernel.org \
    --cc=sdf@google.com \
    --cc=stephen@networkplumber.org \
    /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).