From: "Arnd Bergmann" <arnd@arndb.de>
To: "Qingfang Deng" <dqfext@gmail.com>,
linux-ppp@vger.kernel.org,
"Michal Ostrowski" <mostrows@earthlink.net>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: "Michal Ostrowski" <mostrows@gmail.com>,
"Dianne Skoll" <dianne@skoll.ca>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Jaco Kroon" <jaco@uls.co.za>,
"James Carlson" <carlsonj@workingcode.com>,
"Guillaume Nault" <gnault@redhat.com>
Subject: Re: [PATCH RFC net-next v2] pppoe: remove kernel-mode relay support
Date: Fri, 13 Feb 2026 11:11:05 +0100 [thread overview]
Message-ID: <2c34fb08-15ad-4aec-b429-d1e364a27c8c@app.fastmail.com> (raw)
In-Reply-To: <20260213091605.132561-1-dqfext@gmail.com>
On Fri, Feb 13, 2026, at 10:16, Qingfang Deng wrote:
> The kernel-mode PPPoE relay feature and its two associated ioctls
> (PPPOEIOCSFWD and PPPOEIOCDFWD) are not used by any existing userspace
> PPPoE implementations. The most commonly-used package, RP-PPPoE [1],
> handles the relaying entirely in userspace.
>
> This legacy code has remained in the driver since its introduction in
> kernel 2.3.99-pre7 for over two decades, but has served no practical
> purpose.
>
> Remove the unused relay code.
>
> [1] https://dianne.skoll.ca/projects/rp-pppoe/
>
> Signed-off-by: Qingfang Deng <dqfext@gmail.com>
> ---
> v1: restore .compat_ioctl
> https://lore.kernel.org/linux-ppp/20260211075547.138904-1-dqfext@gmail.com/
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2026-02-13 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 9:16 Qingfang Deng
2026-02-13 10:11 ` Arnd Bergmann [this message]
2026-02-19 14:06 ` Guillaume Nault
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=2c34fb08-15ad-4aec-b429-d1e364a27c8c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrew+netdev@lunn.ch \
--cc=carlsonj@workingcode.com \
--cc=davem@davemloft.net \
--cc=dianne@skoll.ca \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=jaco@uls.co.za \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=mostrows@earthlink.net \
--cc=mostrows@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulus@ozlabs.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
all inboxes | Powered by JetHome®