[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aRyMcF3tg563bQTP@zx2c4.com>
Date: Tue, 18 Nov 2025 16:10:40 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Asbjørn Sloth Tønnesen <ast@...erby.net>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Donald Hunter <donald.hunter@...il.com>,
Simon Horman <horms@...nel.org>,
Jacob Keller <jacob.e.keller@...el.com>,
Andrew Lunn <andrew+netdev@...n.ch>, wireguard@...ts.zx2c4.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Jordan Rife <jordan@...fe.io>
Subject: Re: [PATCH net-next v3 06/11] uapi: wireguard: move flag enums
On Wed, Nov 05, 2025 at 06:32:15PM +0000, Asbjørn Sloth Tønnesen wrote:
> Move the wg*_flag enums, so that they are defined above the
> attribute set enums, as ynl-gen would place them.
>
> This is an incremental step towards adopting an UAPI header
> generated by ynl-gen. This is split out to keep the patches readable.
>
> This is a trivial patch with no behavioural changes intended.
Can we call the subject of this commit `wireguard: uapi: ...`, and same
for the other one?
Powered by blists - more mailing lists