All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: mkubecek@suse.cz
Cc: netdev@vger.kernel.org, ant.v.moryakov@gmail.com
Subject: Re: [PATCH ethtool] netlink: fix missing headers in text output
Date: Tue, 15 Jul 2025 06:40:10 -0700	[thread overview]
Message-ID: <20250715064010.164c1c4b@kernel.org> (raw)
In-Reply-To: <20250712145105.4066308-1-kuba@kernel.org>

On Sat, 12 Jul 2025 07:51:05 -0700 Jakub Kicinski wrote:
> The commit under fixes added a NULL-check which prevents us from
> printing text headers. Conversions to add JSON support often use:

Hi Michal! 
Would you be able to apply this ASAP and cut a release?
AFAICT this bug has made its way to Fedora, at least.
And some scripts try to match on the section text..

  reply	other threads:[~2025-07-15 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-12 14:51 [PATCH ethtool] netlink: fix missing headers in text output Jakub Kicinski
2025-07-15 13:40 ` Jakub Kicinski [this message]
2025-07-17 12:04   ` Michal Kubecek
2025-07-21 22:30 ` patchwork-bot+netdevbpf
     [not found] <0bcad81d1d004c74abfbb73eacbe6ec2@amazon.com>
2025-07-15 11:52 ` Arinzon, David

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=20250715064010.164c1c4b@kernel.org \
    --to=kuba@kernel.org \
    --cc=ant.v.moryakov@gmail.com \
    --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.