public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: linux-ppp@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, julianbraha@gmail.com, ebiggers@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	paulus@ozlabs.org, dianne@skoll.ca, jaco@uls.co.za,
	carlsonj@workingcode.com
Subject: Re: [PATCH net-next v2] ppp: update Kconfig help message
Date: Fri, 03 Apr 2026 23:10:43 +0000	[thread overview]
Message-ID: <177525784378.1484550.10647579476191205570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260402050053.144250-1-qingfang.deng@linux.dev>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  2 Apr 2026 13:00:50 +0800 you wrote:
> Both links of the PPPoE section are no longer valid, and the CVS version
> is no longer relevant.
> 
> - Replace the TLDP URL with the pppd project homepage.
> - Update pppd version requirement for PPPoE.
> - Update RP-PPPoE project homepage, and clarify that it's only needed
>   for server mode.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] ppp: update Kconfig help message
    https://git.kernel.org/netdev/net-next/c/779fae61a3c8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-03 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  5:00 [PATCH net-next v2] ppp: update Kconfig help message Qingfang Deng
2026-04-02  6:04 ` Jaco Kroon
2026-04-02 14:43 ` Julian Braha
2026-04-03 23:10 ` 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=177525784378.1484550.10647579476191205570.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=carlsonj@workingcode.com \
    --cc=davem@davemloft.net \
    --cc=dianne@skoll.ca \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=jaco@uls.co.za \
    --cc=julianbraha@gmail.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 \
    --cc=qingfang.deng@linux.dev \
    /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