From: Jaco Kroon <jaco@uls.co.za>
To: Dianne Skoll <dianne@skoll.ca>
Cc: Qingfang Deng <dqfext@gmail.com>,
linux-ppp@vger.kernel.org, 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>,
Eric Biggers <ebiggers@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@ozlabs.org>,
James Carlson <carlsonj@workingcode.com>
Subject: Re: [PATCH net-next] pppoe: update Kconfig URLs
Date: Tue, 31 Mar 2026 16:21:30 +0200 [thread overview]
Message-ID: <1bba860e-a204-4a5b-9b8f-4d55a559d01e@uls.co.za> (raw)
In-Reply-To: <20260331091655.30212333@gato.skoll.ca>
Hi Dianne,
On 2026/03/31 15:16, Dianne Skoll wrote:
> On Tue, 31 Mar 2026 08:21:40 +0200
> Jaco Kroon <jaco@uls.co.za> wrote:
>
>> That same code has recently been dropped from rp-pppoe,
> That is not the case. I still ship all of the plugin code with rp-pppoe.
My bad, my apologies. It was the userspace code you dropped then, which
does NOT require the kernel options? I do recall there was a huge
debate around this though in the one ppp bug.
>> Most people will never need rp-pppoe.
> This is correct because the ppp project *also* ships the plugin code.
Kind regards,
Jaco
next prev parent reply other threads:[~2026-03-31 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 3:33 Qingfang Deng
2026-03-31 6:21 ` Jaco Kroon
2026-03-31 7:54 ` Qingfang Deng
2026-03-31 8:08 ` Jaco Kroon
2026-03-31 8:49 ` Qingfang Deng
2026-03-31 13:16 ` Dianne Skoll
2026-03-31 14:21 ` Jaco Kroon [this message]
2026-03-31 14:25 ` Dianne Skoll
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=1bba860e-a204-4a5b-9b8f-4d55a559d01e@uls.co.za \
--to=jaco@uls.co.za \
--cc=andrew+netdev@lunn.ch \
--cc=carlsonj@workingcode.com \
--cc=davem@davemloft.net \
--cc=dianne@skoll.ca \
--cc=dqfext@gmail.com \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--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®