From: patchwork-bot+netdevbpf@kernel.org
To: Richard Gobert <richardbgobert@gmail.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
johannes@sipsolutions.net, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, imagedong@tencent.com, kafai@fb.com,
asml.silence@gmail.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] net-next: skbuff: refactor pskb_pull
Date: Fri, 30 Sep 2022 11:40:18 +0000 [thread overview]
Message-ID: <166453801824.4225.1578250985659181646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220928125522.GA100793@debian>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 28 Sep 2022 14:55:31 +0200 you wrote:
> pskb_may_pull already contains all of the checks performed by
> pskb_pull.
> Use pskb_may_pull for validation in pskb_pull, eliminating the
> duplication and making __pskb_pull obsolete.
> Replace __pskb_pull with pskb_pull where applicable.
>
> Signed-off-by: Richard Gobert <richardbgobert@gmail.com>
>
> [...]
Here is the summary with links:
- net-next: skbuff: refactor pskb_pull
https://git.kernel.org/netdev/net-next/c/d427c8999b07
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:[~2022-09-30 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:55 [PATCH] net-next: skbuff: refactor pskb_pull Richard Gobert
2022-09-30 11:40 ` 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=166453801824.4225.1578250985659181646.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=imagedong@tencent.com \
--cc=johannes@sipsolutions.net \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=steffen.klassert@secunet.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).