From: Jakub Kicinski <kuba@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
donald.hunter@redhat.com
Subject: Re: [RFC net-next v1] tools: ynl: Add an strace rendering mode to ynl-gen
Date: Fri, 23 Jun 2023 08:28:18 -0700 [thread overview]
Message-ID: <20230623082818.4e815793@kernel.org> (raw)
In-Reply-To: <m2mt0q9ygf.fsf@gmail.com>
On Fri, 23 Jun 2023 13:04:32 +0100 Donald Hunter wrote:
> > Fair point. Our own names would be easier to understand -- OTOH I like
> > how the print formats almost forcefully drive the point that these are
> > supposed to be used exclusively for printing.
> >
> > If someone needs to interpret the data they should add a struct.
> >
> > But I guess a big fat warning above the documentation and calling the
> > attribute "print-format" / "print-hint" could work as well? Up to you.
> >
> > Hope this makes sense.
>
> Does "display-hint" sound okay? Maybe me being a bit fussy vs
> "print-hint" but it feels more appropriate to me.
Sounds good.
> > If we're only talking about printing we will want to extend the support
> > to new families as well.
>
> Yep, makes sense. Is there any magic/scripted way of keeping the
> different schemas in sync or do they just get modified independently?
Nope :(
prev parent reply other threads:[~2023-06-23 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 15:13 [RFC net-next v1] tools: ynl: Add an strace rendering mode to ynl-gen Donald Hunter
2023-06-15 17:19 ` Simon Horman
2023-06-16 3:00 ` Jakub Kicinski
2023-06-16 10:17 ` Donald Hunter
2023-06-16 18:11 ` Jakub Kicinski
2023-06-19 10:04 ` Donald Hunter
2023-06-19 19:00 ` Jakub Kicinski
2023-06-23 12:04 ` Donald Hunter
2023-06-23 15:28 ` Jakub Kicinski [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=20230623082818.4e815793@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).