From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jiri Pirko <jiri@resnulli.us>,
"Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, saeedm@nvidia.com, leon@kernel.org,
richardcochran@gmail.com, jonathan.lemon@gmail.com,
netdev@vger.kernel.org
Subject: Re: [patch net-next] dpll: remove leftover mode_supported() op and use mode_get() instead
Date: Fri, 8 Dec 2023 12:06:34 +0000 [thread overview]
Message-ID: <49d5c768-2a05-4f20-99cf-a92aa378ebdd@linux.dev> (raw)
In-Reply-To: <20231207151204.1007797-1-jiri@resnulli.us>
On 07/12/2023 15:12, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Mode supported is currently reported to the user exactly the same, as
> the current mode. That's because mode changing is not implemented.
> Remove the leftover mode_supported() op and use mode_get() to fill up
> the supported mode exposed to user.
>
> One, if even, mode changing is going to be introduced, this could be
> very easily taken back. In the meantime, prevent drivers form
> implementing this in wrong way (as for example recent netdevsim
> implementation attempt intended to do).
>
I'm OK to remove from ptp_ocp part because it's really only one mode
supported. But I would like to hear something from Arkadiusz about the
plans to maybe implement mode change in ice?
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> ---
> drivers/dpll/dpll_netlink.c | 16 +++++++-----
> drivers/net/ethernet/intel/ice/ice_dpll.c | 26 -------------------
> .../net/ethernet/mellanox/mlx5/core/dpll.c | 9 -------
> drivers/ptp/ptp_ocp.c | 8 ------
> include/linux/dpll.h | 3 ---
> 5 files changed, 10 insertions(+), 52 deletions(-)
>
next prev parent reply other threads:[~2023-12-08 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 15:12 [patch net-next] dpll: remove leftover mode_supported() op and use mode_get() instead Jiri Pirko
2023-12-08 12:06 ` Vadim Fedorenko [this message]
2023-12-09 10:37 ` Jiri Pirko
2023-12-12 20:22 ` Simon Horman
2023-12-13 10:40 ` patchwork-bot+netdevbpf
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=49d5c768-2a05-4f20-99cf-a92aa378ebdd@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).