public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dianne Skoll <dianne@skoll.ca>
To: Jaco Kroon <jaco@uls.co.za>
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 10:25:08 -0400	[thread overview]
Message-ID: <20260331102508.2eb6dce8@gato.skoll.ca> (raw)
In-Reply-To: <1bba860e-a204-4a5b-9b8f-4d55a559d01e@uls.co.za>

Hi, all,

> My bad, my apologies. It was the userspace code you dropped then, which 
> does NOT require the kernel options?

I was considering doing that, but I kept the userspace code.  The reason is
that on some platforms, such as uclinux on a processor without an MMU,
the dlopen() system call is not implemented, so there's no way to use
a plugin with pppd.  One user asked me to keep the userspace code, so I
did.

But you are correct in that 99.99% of Linux users will not need to download
rp-pppoe if all they want to do is connect to the Internet using a PPPoE
client.

Regards,

Dianne.

      reply	other threads:[~2026-03-31 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  3:33 [PATCH net-next] pppoe: update Kconfig URLs 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
2026-03-31 14:25       ` Dianne Skoll [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=20260331102508.2eb6dce8@gato.skoll.ca \
    --to=dianne@skoll.ca \
    --cc=andrew+netdev@lunn.ch \
    --cc=carlsonj@workingcode.com \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=jaco@uls.co.za \
    --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