From: patchwork-bot+netdevbpf@kernel.org
To: l00371289 <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, alobakin@pm.me,
jonathan.lemon@gmail.com, willemb@google.com,
linmiaohe@huawei.com, gnault@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@openeuler.org
Subject: Re: [PATCH net-next] skbuff: remove some unnecessary operation in skb_segment_list()
Date: Wed, 10 Mar 2021 21:00:13 +0000 [thread overview]
Message-ID: <161541001340.4631.1104873444053085723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1615364938-52943-1-git-send-email-linyunsheng@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 10 Mar 2021 16:28:58 +0800 you wrote:
> From: Yunsheng Lin <linyunsheng@huawei.com>
>
> gro list uses skb_shinfo(skb)->frag_list to link two skb together,
> and NAPI_GRO_CB(p)->last->next is used when there are more skb,
> see skb_gro_receive_list(). gso expects that each segmented skb is
> linked together using skb->next, so only the first skb->next need
> to set to skb_shinfo(skb)-> frag_list when doing gso list segment.
>
> [...]
Here is the summary with links:
- [net-next] skbuff: remove some unnecessary operation in skb_segment_list()
https://git.kernel.org/netdev/net-next/c/1ddc3229ad3c
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:[~2021-03-10 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 8:28 [PATCH net-next] skbuff: remove some unnecessary operation in skb_segment_list() l00371289
2021-03-10 21:00 ` 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=161541001340.4631.1104873444053085723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=davem@davemloft.net \
--cc=gnault@redhat.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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).