From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, gospo@broadcom.com,
gustavo@embeddedor.com
Subject: Re: [PATCH net-next 0/2] bnxt_en: Fix 2 compile warnings in bnxt_dcb.c
Date: Tue, 08 Aug 2023 22:10:26 +0000 [thread overview]
Message-ID: <169153262645.13746.15905080876234597676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807145720.159645-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Aug 2023 07:57:18 -0700 you wrote:
> Fix 2 similar warnings in bnxt_dcb.c related to the cos2bw interface
> definitions in bnxt_hsi.h.
>
> Michael Chan (2):
> bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy()
> bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c
>
> [...]
Here is the summary with links:
- [net-next,1/2] bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy()
https://git.kernel.org/netdev/net-next/c/ac1b8c978a7a
- [net-next,2/2] bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c
https://git.kernel.org/netdev/net-next/c/3d5ecada049f
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-08-08 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:57 [PATCH net-next 0/2] bnxt_en: Fix 2 compile warnings in bnxt_dcb.c Michael Chan
2023-08-07 14:57 ` [PATCH net-next 1/2] bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy() Michael Chan
2023-08-08 11:16 ` Gustavo A. R. Silva
2023-08-07 14:57 ` [PATCH net-next 2/2] bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c Michael Chan
2023-08-08 11:18 ` Gustavo A. R. Silva
2023-08-08 22: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=169153262645.13746.15905080876234597676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=gustavo@embeddedor.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).