From: John Crispin <john@phrozen.org>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
Christian Marangi <ansuelsmth@gmail.com>
Subject: [RFC net-next 10/12] net: pon: build the PON subsystem
Date: Thu, 8 Oct 2026 16:32:47 +0200 [thread overview]
Message-ID: <20261008143249.3439762-11-john@phrozen.org> (raw)
In-Reply-To: <20261008143249.3439762-1-john@phrozen.org>
Add CONFIG_PON (a tristate) and the Makefile of the core. Hook net/pon
into net/Kconfig and net/Makefile.
The build is wired last, so every commit before it builds and the
series bisects.
Assisted-by: LLM
Signed-off-by: John Crispin <john@phrozen.org>
---
net/Kconfig | 1 +
net/Makefile | 1 +
net/pon/Kconfig | 17 +++++++++++++++++
net/pon/Makefile | 6 ++++++
4 files changed, 25 insertions(+)
create mode 100644 net/pon/Kconfig
create mode 100644 net/pon/Makefile
diff --git a/net/Kconfig b/net/Kconfig
index 76ab44aa439a..117845100a06 100644
--- a/net/Kconfig
+++ b/net/Kconfig
@@ -82,6 +82,7 @@ menu "Networking options"
source "net/packet/Kconfig"
source "net/psp/Kconfig"
+source "net/pon/Kconfig"
source "net/unix/Kconfig"
source "net/tls/Kconfig"
source "net/xfrm/Kconfig"
diff --git a/net/Makefile b/net/Makefile
index 5b2dd7f07a85..757650c5428d 100644
--- a/net/Makefile
+++ b/net/Makefile
@@ -19,6 +19,7 @@ obj-$(CONFIG_TLS) += tls/
obj-$(CONFIG_XFRM) += xfrm/
obj-$(CONFIG_UNIX) += unix/
obj-$(CONFIG_INET_PSP) += psp/
+obj-$(CONFIG_PON) += pon/
obj-y += ipv6/
obj-$(CONFIG_PACKET) += packet/
obj-$(CONFIG_NET_KEY) += key/
diff --git a/net/pon/Kconfig b/net/pon/Kconfig
new file mode 100644
index 000000000000..af40d4ebd938
--- /dev/null
+++ b/net/pon/Kconfig
@@ -0,0 +1,17 @@
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# PON subsystem configuration
+#
+config PON
+ tristate "Passive Optical Network (PON) device support"
+ depends on NET
+ help
+ Enable kernel support for PON (GPON / XG(S)-PON) ONU devices: the
+ netlink configuration family (which also carries the OMCI
+ management channel to a userspace OMCI stack) and per GEM port
+ virtual devices.
+
+ To compile this as a module, choose M here: the module will be
+ called pon.
+
+ If unsure, say N.
diff --git a/net/pon/Makefile b/net/pon/Makefile
new file mode 100644
index 000000000000..4b23d2265be9
--- /dev/null
+++ b/net/pon/Makefile
@@ -0,0 +1,6 @@
+# SPDX-License-Identifier: GPL-2.0-only
+
+obj-$(CONFIG_PON) += pon.o
+
+pon-y := pon_main.o pon_nl.o pon_omci.o pon_gem.o pon_conduit.o \
+ pon_work.o pon_state.o pon_ploam_msg.o pon-nl-gen.o
--
2.34.1
next prev parent reply other threads:[~2026-10-08 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 14:32 [RFC net-next 00/12] net: add " John Crispin
2026-10-08 14:32 ` [RFC net-next 01/12] net: pon: add the netlink specification of the pon family John Crispin
2026-10-08 14:32 ` [RFC net-next 02/12] net: add a PON device pointer to struct net_device John Crispin
2026-10-08 14:32 ` [RFC net-next 03/12] net: pon: add the PLOAM vocabulary and message codec John Crispin
2026-10-08 14:32 ` [RFC net-next 04/12] net: pon: add the device state and the lent context John Crispin
2026-10-08 14:32 ` [RFC net-next 05/12] net: pon: add the conduit contract John Crispin
2026-10-08 14:32 ` [RFC net-next 06/12] net: pon: add the GEM network devices John Crispin
2026-10-08 14:32 ` [RFC net-next 07/12] net: pon: add the OMCI channel John Crispin
2026-10-08 14:32 ` [RFC net-next 08/12] net: pon: add netlink support John Crispin
2026-10-08 14:32 ` [RFC net-next 09/12] net: pon: add the device registration John Crispin
2026-10-08 14:32 ` John Crispin [this message]
2026-10-08 14:32 ` [RFC net-next 11/12] Documentation: networking: describe the PON subsystem John Crispin
2026-10-08 14:32 ` [RFC net-next 12/12] MAINTAINERS: add " John Crispin
2026-10-09 2:27 ` [RFC net-next 00/12] net: " Gaoyang Wei
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=20261008143249.3439762-11-john@phrozen.org \
--to=john@phrozen.org \
--cc=andrew+netdev@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®