From: patchwork-bot+netdevbpf@kernel•org
To: Petr Machata <petrm@nvidia•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, netdev@vger•kernel.org, idosch@nvidia•com,
mlxsw@nvidia•com
Subject: Re: [PATCH net-next 0/2] mlxsw: Fix -Wformat-truncation warnings
Date: Tue, 10 Oct 2023 10:20:25 +0000 [thread overview]
Message-ID: <169693322578.26630.2632330656608204931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1696600763.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Fri, 6 Oct 2023 16:43:15 +0200 you wrote:
> Ido Schimmel writes:
>
> Commit 6d4ab2e97dcf ("extrawarn: enable format and stringop overflow
> warnings in W=1") enabled format warnings as part of W=1 builds,
> resulting in two new warnings in mlxsw. Fix both and target at net-next
> as the warnings are not indicative of actual bugs.
>
> [...]
Here is the summary with links:
- [net-next,1/2] mlxsw: core_thermal: Fix -Wformat-truncation warning
https://git.kernel.org/netdev/net-next/c/83b2d81b691c
- [net-next,2/2] mlxsw: spectrum_ethtool: Fix -Wformat-truncation warning
https://git.kernel.org/netdev/net-next/c/392ce2abb0ce
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-10-10 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 14:43 [PATCH net-next 0/2] mlxsw: Fix -Wformat-truncation warnings Petr Machata
2023-10-06 14:43 ` [PATCH net-next 1/2] mlxsw: core_thermal: Fix -Wformat-truncation warning Petr Machata
2023-10-06 14:43 ` [PATCH net-next 2/2] mlxsw: spectrum_ethtool: " Petr Machata
2023-10-08 13:59 ` [PATCH net-next 0/2] mlxsw: Fix -Wformat-truncation warnings Simon Horman
2023-10-10 10:20 ` 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=169693322578.26630.2632330656608204931.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mlxsw@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(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