netdev - Re: [PATCH net-next v2 01/13] netlink: specs: rename rtnetlink specs in accordance with family name

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: <20250410182817.7e0b838d@kernel.org>
Date: Thu, 10 Apr 2025 18:28:17 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Donald Hunter <donald.hunter@...il.com>
Cc: Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
 edumazet@...gle.com, andrew+netdev@...n.ch, horms@...nel.org,
 jacob.e.keller@...el.com, yuyanghuang@...gle.com, sdf@...ichev.me,
 gnault@...hat.com, nicolas.dichtel@...nd.com, petrm@...dia.com, "David S.
 Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next v2 01/13] netlink: specs: rename rtnetlink
 specs in accordance with family name

On Thu, 10 Apr 2025 13:39:17 +0100 Donald Hunter wrote:
> Yes, Documentation/Makefile goes the extra mile to only try deleting a
> list of .rst files generated from the list of source .yaml files. It
> would be easier to just delete
> Documentation/networking/netlink_spec/*.rst which would be able to
> clean up old generated files in situations like this.

Hm, that would work. I think it's only the second time we hit this
problem, tho, so I'm just going to apply and clean up manually.
If it happens again I can change the build script..