netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, Ido Schimmel <idosch@nvidia.com>,
	mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/2] mlxsw: Fix -Wformat-truncation warnings
Date: Sun, 8 Oct 2023 15:59:37 +0200	[thread overview]
Message-ID: <20231008135937.GH831234@kernel.org> (raw)
In-Reply-To: <cover.1696600763.git.petrm@nvidia.com>

On Fri, Oct 06, 2023 at 04:43:15PM +0200, Petr Machata 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.
> 
> Ido Schimmel (2):
>   mlxsw: core_thermal: Fix -Wformat-truncation warning
>   mlxsw: spectrum_ethtool: Fix -Wformat-truncation warning

For series,

Reviewed-by: Simon Horman <horms@kernel.org>
Tested-by: Simon Horman <horms@kernel.org> # build-tested


  parent reply	other threads:[~2023-10-08 13:59 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 ` Simon Horman [this message]
2023-10-10 10:20 ` [PATCH net-next 0/2] mlxsw: Fix -Wformat-truncation warnings patchwork-bot+netdevbpf

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=20231008135937.GH831234@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.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).