From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: aelior@marvell.com, GR-everest-linux-l2@marvell.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] qede: Remove a erroneous ++ in 'qede_rx_build_jumbo()'
Date: Mon, 05 Apr 2021 20:00:09 +0000 [thread overview]
Message-ID: <161765280958.6353.3809782901793052721.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1c27abb938a430e58bd644729597015b3414d4aa.1617540100.git.christophe.jaillet@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sun, 4 Apr 2021 14:42:44 +0200 you wrote:
> This ++ is confusing. It looks duplicated with the one already performed in
> 'skb_fill_page_desc()'.
>
> In fact, it is harmless. 'nr_frags' is written twice with the same value.
> Once, because of the nr_frags++, and once because of the 'nr_frags = i + 1'
> in 'skb_fill_page_desc()'.
>
> [...]
Here is the summary with links:
- [1/2] qede: Remove a erroneous ++ in 'qede_rx_build_jumbo()'
https://git.kernel.org/netdev/net-next/c/1ec3d02f9cdf
- [2/2] qede: Use 'skb_add_rx_frag()' instead of hand coding it
https://git.kernel.org/netdev/net-next/c/7190e9d8e131
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-04-05 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 12:42 Christophe JAILLET
2021-04-04 12:42 ` [PATCH 2/2] qede: Use 'skb_add_rx_frag()' instead of hand coding it Christophe JAILLET
2021-04-05 10:07 ` [EXT] " Manish Chopra
2021-04-05 10:01 ` [EXT] [PATCH 1/2] qede: Remove a erroneous ++ in 'qede_rx_build_jumbo()' Manish Chopra
2021-04-05 20: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=161765280958.6353.3809782901793052721.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®