[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231009082243.6a195cc1@kernel.org>
Date: Mon, 9 Oct 2023 08:22:43 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
netdev@...r.kernel.org, vadim.fedorenko@...ux.dev, corbet@....net,
davem@...emloft.net, pabeni@...hat.com, jesse.brandeburg@...el.com,
anthony.l.nguyen@...el.com, linux-doc@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org
Subject: Re: [PATCH net-next v3 2/5] dpll: spec: add support for pin-dpll
signal phase offset/adjust
On Sat, 7 Oct 2023 12:29:47 +0200 Jiri Pirko wrote:
> But since by the policy we cannot break uapi compat, version should be
> never bumped. I wonder howcome it is legit in the examples you listed
> above...
Yes, even it's the 0.0001% of the time when "breaking' uAPI is fine,
the change in the family spec can these days be much more precisely
detected using policy dump.
> Let's forbid that in genetlink.yaml. I have a patch ready, please ack
> this approach.
Ack, please remember to move version into the # Start genetlink-legacy
section in the genetlink-legacy schema.
Powered by blists - more mailing lists