netdev - Re: [RFC net-next v1] tools: ynl: Add an strace rendering mode to ynl-gen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230623082818.4e815793@kernel.org>
Date: Fri, 23 Jun 2023 08:28:18 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Donald Hunter <donald.hunter@...il.com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 donald.hunter@...hat.com
Subject: Re: [RFC net-next v1] tools: ynl: Add an strace rendering mode to
 ynl-gen

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 :(