From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <dqfext@gmail.com>
Cc: linux-ppp@vger.kernel.org, mostrows@earthlink.net,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mostrows@gmail.com,
dianne@skoll.ca, paulus@ozlabs.org, jaco@uls.co.za,
carlsonj@workingcode.com, arnd@arndb.de, gnault@redhat.com
Subject: Re: [PATCH net-next] pppoe: remove kernel-mode relay support
Date: Thu, 26 Feb 2026 10:50:05 +0000 [thread overview]
Message-ID: <177210300529.1158350.17223286559184798154.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260224015053.42472-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 24 Feb 2026 09:50:52 +0800 you 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.
>
> [...]
Here is the summary with links:
- [net-next] pppoe: remove kernel-mode relay support
https://git.kernel.org/netdev/net-next/c/15c9ed1d8286
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-26 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:50 [PATCH net-next] pppoe: remove kernel-mode relay support Qingfang Deng
2026-02-26 10:50 ` patchwork-bot+netdevbpf [this message]
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=177210300529.1158350.17223286559184798154.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--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