From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kees@kernel.org,
gnault@redhat.com, ericwouds@gmail.com,
dawid.osuchowski@linux.intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-ppp@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] pppox: remove sk_pppox() helper
Date: Sun, 12 Apr 2026 22:30:09 +0000 [thread overview]
Message-ID: <177603300979.3841629.1311062865318467682.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260410054954.114031-1-qingfang.deng@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 Apr 2026 13:49:49 +0800 you wrote:
> The sk member can be directly accessed from struct pppox_sock without
> relying on type casting. Remove the sk_pppox() helper and update all
> call sites to use po->sk directly.
>
> Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>
> ---
> Changes in v2: none
> Link to v1: https://lore.kernel.org/r/20260408015138.280687-1-qingfang.deng@linux.dev
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] pppox: remove sk_pppox() helper
https://git.kernel.org/netdev/net-next/c/105369d627b9
- [net-next,v2,2/2] pppox: convert pppox_sk() to use container_of()
https://git.kernel.org/netdev/net-next/c/6bc78039a77a
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-04-12 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 5:49 [PATCH net-next v2 1/2] pppox: remove sk_pppox() helper Qingfang Deng
2026-04-10 5:49 ` [PATCH net-next v2 2/2] pppox: convert pppox_sk() to use container_of() Qingfang Deng
2026-04-12 22:30 ` 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=177603300979.3841629.1311062865318467682.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dawid.osuchowski@linux.intel.com \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--cc=gnault@redhat.com \
--cc=kees@kernel.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.