From: Stephen Hemminger <stephen@networkplumber.org>
To: Quentin Deslandes <qde@naccy.de>
Cc: <netdev@vger.kernel.org>, David Ahern <dsahern@gmail.com>,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH 0/3] ss: pretty-printing BPF socket-local storage
Date: Fri, 8 Dec 2023 09:27:01 -0800 [thread overview]
Message-ID: <20231208092701.52101740@hermes.local> (raw)
In-Reply-To: <7f656048-314b-4c04-bc2e-cd29ab649f8b@naccy.de>
On Fri, 8 Dec 2023 16:01:56 +0100
Quentin Deslandes <qde@naccy.de> wrote:
> I've submitted a v2 to fix Martin's comments and also improve the printing
> behavior. The updated revision reduces the number of lines added by 50%.
Not sure about what best format for this is.
>
> Regarding the JSON output, is it specifically for socket-local storage, or
> more generally, for the whole tool? I agree with you anyway, but I would argue
> that it doesn't fit this series, although I can work on this as a next step.
It is more for the whole tool in future.
prev parent reply other threads:[~2023-12-08 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 2:30 [PATCH 0/3] ss: pretty-printing BPF socket-local storage Quentin Deslandes
2023-11-28 2:30 ` [PATCH 1/3] ss: prevent "Process" column from being printed unless requested Quentin Deslandes
2023-11-29 0:20 ` David Ahern
2023-11-28 2:30 ` [PATCH 2/3] ss: add support for BPF socket-local storage Quentin Deslandes
2023-11-28 23:35 ` Martin KaFai Lau
2023-11-28 2:30 ` [PATCH 3/3] ss: pretty-print " Quentin Deslandes
2023-11-28 23:42 ` Martin KaFai Lau
2023-11-28 22:43 ` [PATCH 0/3] ss: pretty-printing " Stephen Hemminger
2023-12-08 15:01 ` Quentin Deslandes
2023-12-08 17:27 ` Stephen Hemminger [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=20231208092701.52101740@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qde@naccy.de \
/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).