From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: vadim.fedorenko@linux.dev, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
jesse.brandeburg@intel.com,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
anthony.l.nguyen@intel.com, intel-wired-lan@lists.osuosl.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v3 2/5] dpll: spec: add support for pin-dpll signal phase offset/adjust
Date: Mon, 9 Oct 2023 08:22:43 -0700 [thread overview]
Message-ID: <20231009082243.6a195cc1@kernel.org> (raw)
In-Reply-To: <ZSEzG0TpTI6W9+tL@nanopsycho>
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.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
corbet@lwn.net, davem@davemloft.net, pabeni@redhat.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
linux-doc@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next v3 2/5] dpll: spec: add support for pin-dpll signal phase offset/adjust
Date: Mon, 9 Oct 2023 08:22:43 -0700 [thread overview]
Message-ID: <20231009082243.6a195cc1@kernel.org> (raw)
In-Reply-To: <ZSEzG0TpTI6W9+tL@nanopsycho>
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.
next prev parent reply other threads:[~2023-10-09 15:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 11:40 [Intel-wired-lan] [PATCH net-next v3 0/5] dpll: add phase-offset and phase-adjust Arkadiusz Kubalewski
2023-10-06 11:40 ` Arkadiusz Kubalewski
2023-10-06 11:40 ` [Intel-wired-lan] [PATCH net-next v3 1/5] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-10-06 11:40 ` Arkadiusz Kubalewski
2023-10-06 11:40 ` [Intel-wired-lan] [PATCH net-next v3 2/5] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-10-06 11:40 ` Arkadiusz Kubalewski
2023-10-06 12:30 ` [Intel-wired-lan] " Jiri Pirko
2023-10-06 12:30 ` Jiri Pirko
2023-10-06 14:55 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-06 14:55 ` Jakub Kicinski
2023-10-06 16:53 ` [Intel-wired-lan] " Jiri Pirko
2023-10-06 16:53 ` Jiri Pirko
2023-10-06 19:44 ` [Intel-wired-lan] " Kuba Kicinski
2023-10-06 19:44 ` Kuba Kicinski
2023-10-07 10:29 ` [Intel-wired-lan] " Jiri Pirko
2023-10-07 10:29 ` Jiri Pirko
2023-10-09 15:22 ` Jakub Kicinski [this message]
2023-10-09 15:22 ` Jakub Kicinski
2023-10-09 22:55 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-09 22:55 ` Kubalewski, Arkadiusz
2023-10-06 11:40 ` [Intel-wired-lan] [PATCH net-next v3 3/5] dpll: netlink/core: " Arkadiusz Kubalewski
2023-10-06 11:40 ` Arkadiusz Kubalewski
2023-10-06 12:38 ` [Intel-wired-lan] " Jiri Pirko
2023-10-06 12:38 ` Jiri Pirko
2023-10-09 22:49 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-09 22:49 ` Kubalewski, Arkadiusz
2023-10-06 11:41 ` [Intel-wired-lan] [PATCH net-next v3 4/5] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-10-06 11:41 ` Arkadiusz Kubalewski
2023-10-06 12:33 ` [Intel-wired-lan] " Simon Horman
2023-10-06 12:33 ` Simon Horman
2023-10-06 12:41 ` [Intel-wired-lan] " Jiri Pirko
2023-10-06 12:41 ` Jiri Pirko
2023-10-06 11:41 ` [Intel-wired-lan] [PATCH net-next v3 5/5] dpll: netlink/core: change pin frequency set behavior Arkadiusz Kubalewski
2023-10-06 11:41 ` Arkadiusz Kubalewski
2023-10-06 12:35 ` [Intel-wired-lan] " Jiri Pirko
2023-10-06 12:35 ` Jiri Pirko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231009082243.6a195cc1@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.