From: Jakub Kicinski <kuba@kernel•org>
To: Andrew Lunn <andrew@lunn•ch>
Cc: Qingfang Deng <dqfext@gmail•com>, Paolo Abeni <pabeni@redhat•com>,
Dianne Skoll <dianne@skoll•ca>, Shuah Khan <shuah@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Simon Horman <horms@kernel•org>,
Felix Maurer <fmaurer@redhat•com>,
Sebastian Andrzej Siewior <bigeasy@linutronix•de>,
"Matthieu Baerts (NGI0)" <matttbe@kernel•org>,
linux-kernel@vger•kernel.org, linux-kselftest@vger•kernel.org,
linux-ppp@vger•kernel.org, netdev@vger•kernel.org,
Paul Mackerras <paulus@ozlabs•org>, Jaco Kroon <jaco@uls•co.za>
Subject: Re: [PATCH net-next v7] selftests: net: add tests for PPP
Date: Thu, 2 Apr 2026 07:55:20 -0700 [thread overview]
Message-ID: <20260402075520.313832ac@kernel.org> (raw)
In-Reply-To: <24aea6cc-d599-4935-8a75-34f38b852d1e@lunn.ch>
On Thu, 2 Apr 2026 16:37:01 +0200 Andrew Lunn wrote:
> > > ln -n /usr/lib64/pppd/2.5.1/pppoe.so /etc/ppp/plugins/rp-pppoe.so
> > >
> > > should solve?
> >
> > Hard links will also work.
> > Alternatively, if your rp-pppoe version is 4.0, you can use the new
> > option `-g` to specify the full path of the pppoe.so plugin.
>
> It should be possible for anybody to run these self tests. So we don't
> want specially crafted setups, but generic setups which will work for
> as many people as possible.
+1 let's try not to tweak the underlying OS.
prev parent reply other threads:[~2026-04-02 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 3:55 [PATCH net-next v7] selftests: net: add tests for PPP Qingfang Deng
2026-04-01 15:10 ` Jakub Kicinski
2026-04-01 15:45 ` Qingfang Deng
2026-04-02 0:56 ` Jakub Kicinski
2026-04-02 2:26 ` Qingfang Deng
2026-04-02 2:52 ` Jakub Kicinski
2026-04-02 9:48 ` Paolo Abeni
2026-04-02 10:13 ` Qingfang Deng
2026-04-02 11:17 ` Paolo Abeni
2026-04-02 12:04 ` Qingfang Deng
2026-04-02 14:37 ` Andrew Lunn
2026-04-02 14:55 ` Jakub Kicinski [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=20260402075520.313832ac@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=dianne@skoll$(echo .)ca \
--cc=dqfext@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=fmaurer@redhat$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jaco@uls$(echo .)co.za \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=matttbe@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paulus@ozlabs$(echo .)org \
--cc=shuah@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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