From: patchwork-bot+netdevbpf@kernel.org
To: YueHaibing <yuehaibing@huawei.com>
Cc: jiawenwu@trustnetic.com, mengyuanlou@net-swift.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: txgbe: Fix two bugs in txgbe_calc_eeprom_checksum
Date: Tue, 08 Nov 2022 04:10:15 +0000 [thread overview]
Message-ID: <166788061557.1355.8749947132220755596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221105080722.20292-1-yuehaibing@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 5 Nov 2022 16:07:20 +0800 you wrote:
> Fix memleak and unsigned comparison bugs in txgbe_calc_eeprom_checksum
>
> YueHaibing (2):
> net: txgbe: Fix memleak in txgbe_calc_eeprom_checksum()
> net: txgbe: Fix unsigned comparison to zero in
> txgbe_calc_eeprom_checksum()
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: txgbe: Fix memleak in txgbe_calc_eeprom_checksum()
https://git.kernel.org/netdev/net-next/c/a068d33e542f
- [net-next,2/2] net: txgbe: Fix unsigned comparison to zero in txgbe_calc_eeprom_checksum()
https://git.kernel.org/netdev/net-next/c/5e2ea7801fac
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-11-08 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 8:07 [PATCH net-next 0/2] net: txgbe: Fix two bugs in txgbe_calc_eeprom_checksum YueHaibing
2022-11-05 8:07 ` [PATCH net-next 1/2] net: txgbe: Fix memleak in txgbe_calc_eeprom_checksum() YueHaibing
2022-11-05 8:07 ` [PATCH net-next 2/2] net: txgbe: Fix unsigned comparison to zero " YueHaibing
2023-07-11 2:47 ` Jiawen Wu
2022-11-08 4:10 ` 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=166788061557.1355.8749947132220755596.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuehaibing@huawei.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