From: patchwork-bot+netdevbpf@kernel•org
To: Yuanjun Gong <ruc_gongyuanjun@163•com>
Cc: kuniyu@amazon•com, ajit.khaparde@broadcom•com,
netdev@vger•kernel.org, somnath.kotur@broadcom•com,
sriharsha.basavapatna@broadcom•com
Subject: Re: [PATCH net v2 1/1] benet: fix return value check in be_lancer_xmit_workarounds()
Date: Thu, 27 Jul 2023 08:50:21 +0000 [thread overview]
Message-ID: <169044782148.5847.13565294652021594404.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725032726.15002-1-ruc_gongyuanjun@163.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Tue, 25 Jul 2023 11:27:26 +0800 you wrote:
> in be_lancer_xmit_workarounds(), it should go to label 'tx_drop'
> if an unexpected value is returned by pskb_trim().
>
> Fixes: 93040ae5cc8d ("be2net: Fix to trim skb for padded vlan packets to workaround an ASIC Bug")
> Signed-off-by: Yuanjun Gong <ruc_gongyuanjun@163•com>
> ---
> drivers/net/ethernet/emulex/benet/be_main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Here is the summary with links:
- [net,v2,1/1] benet: fix return value check in be_lancer_xmit_workarounds()
https://git.kernel.org/netdev/net/c/5c85f7065718
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:[~2023-07-27 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 14:45 [PATCH 1/1] drivers:net: fix return value check in be_lancer_xmit_workarounds Yuanjun Gong
2023-07-17 19:32 ` Kuniyuki Iwashima
2023-07-19 20:16 ` Simon Horman
2023-07-25 3:27 ` [PATCH net v2 1/1] benet: fix return value check in be_lancer_xmit_workarounds() Yuanjun Gong
2023-07-25 18:00 ` Alexander H Duyck
2023-07-27 8:31 ` Paolo Abeni
2023-07-27 8:50 ` 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=169044782148.5847.13565294652021594404.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ajit.khaparde@broadcom$(echo .)com \
--cc=kuniyu@amazon$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ruc_gongyuanjun@163$(echo .)com \
--cc=somnath.kotur@broadcom$(echo .)com \
--cc=sriharsha.basavapatna@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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