linux-kernel - Re: [PATCH net-next 2/6] tools: ynl-gen: refactor render-max enum generation

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <5c944395-141c-415b-b29a-8f70cafaa24d@fiberby.net>
Date: Tue, 14 Oct 2025 17:04:14 +0000
From: Asbjørn Sloth Tønnesen <ast@...erby.net>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 Alexei Starovoitov <ast@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
 Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
 Daniel Borkmann <daniel@...earbox.net>, Daniel Zahka
 <daniel.zahka@...il.com>, Donald Hunter <donald.hunter@...il.com>,
 Jacob Keller <jacob.e.keller@...el.com>,
 Jesper Dangaard Brouer <hawk@...nel.org>, Jiri Pirko <jiri@...nulli.us>,
 Joe Damato <jdamato@...tly.com>, John Fastabend <john.fastabend@...il.com>,
 Jonathan Corbet <corbet@....net>, Simon Horman <horms@...nel.org>,
 Stanislav Fomichev <sdf@...ichev.me>,
 Toke Høiland-Jørgensen <toke@...hat.com>,
 Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
 Willem de Bruijn <willemb@...gle.com>, bpf@...r.kernel.org,
 netdev@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 2/6] tools: ynl-gen: refactor render-max enum
 generation

On 10/14/25 12:58 AM, Jakub Kicinski wrote:
> On Mon, 13 Oct 2025 16:49:59 +0000 Asbjørn Sloth Tønnesen wrote:
>> +        suffix = yaml['type'] == 'flags' and 'mask' or 'max'
> 
> This construct looks highly non-pythonic to me

I don't mind changing it to it's multi-line form, but this line might go
away (see below).

>> +        self.enum_max_name = f'{self.value_pfx}{suffix}'
> 
> sometimes its max sometimes is mask, so we shouldn't call it max always

I'm fine with splitting them to render-max, enum-max-name, render-mask and
enum-mask-name. I was just following along the current lines in the code,
as started in commit 96a611b6b60c.