All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michel Lind <michel@michel-slm.name>
Cc: mkubecek@suse.cz, netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH ethtool] netlink: fix print_string when the value is NULL
Date: Thu, 07 Aug 2025 23:49:02 +0000	[thread overview]
Message-ID: <175461054201.3719041.4355345326392065104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aILUS-BlVm5tubAF@maurice.local>

Hello:

This patch was applied to ethtool/ethtool.git (master)
by Michal Kubecek <mkubecek@suse.cz>:

On Thu, 24 Jul 2025 19:48:11 -0500 you wrote:
> The previous fix in commit b70c92866102 ("netlink: fix missing headers
> in text output") handles the case when value is NULL by still using
> `fprintf` but passing no value.
> 
> This fails if `-Werror=format-security` is passed to gcc, as is the
> default in distros like Fedora.
> 
> [...]

Here is the summary with links:
  - [ethtool] netlink: fix print_string when the value is NULL
    https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=41d6105250c8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-08-07 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  0:48 [PATCH ethtool] netlink: fix print_string when the value is NULL Michel Lind
2025-08-07 23:05 ` Michal Kubecek
2025-08-10  7:14   ` Salvatore Bonaccorso
2025-08-11 20:07     ` Michal Kubecek
2025-08-11 20:23       ` Salvatore Bonaccorso
2025-08-12  6:14         ` Michal Kubecek
2025-08-07 23:49 ` 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=175461054201.3719041.4355345326392065104.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kuba@kernel.org \
    --cc=michel@michel-slm.name \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.