From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, vadim.fedorenko@linux.dev,
arkadiusz.kubalewski@intel.com, saeedm@nvidia.com,
leon@kernel.org, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, rrameshbabu@nvidia.com
Subject: Re: [patch net-next v2 1/3] dpll: extend uapi by lock status error attribute
Date: Thu, 1 Feb 2024 07:02:41 -0800 [thread overview]
Message-ID: <20240201070241.469b0824@kernel.org> (raw)
In-Reply-To: <20240201135311.GE530335@kernel.org>
On Thu, 1 Feb 2024 14:53:11 +0100 Simon Horman wrote:
> > + DPLL_LOCK_STATUS_ERROR_FRACTIONAL_FREQUENCY_OFFSET_TOO_HIGH,
>
> nit: I'm all for descriptive names,
> but this one is rather long to say the least.
OMG :(
next prev parent reply other threads:[~2024-02-01 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 12:08 [patch net-next v2 0/3] dpll: expose lock status error value to user Jiri Pirko
2024-01-30 12:08 ` [patch net-next v2 1/3] dpll: extend uapi by lock status error attribute Jiri Pirko
2024-02-01 13:53 ` Simon Horman
2024-02-01 15:02 ` Jakub Kicinski [this message]
2024-01-30 12:08 ` [patch net-next v2 2/3] dpll: extend lock_status_get() op by status error and expose to user Jiri Pirko
2024-02-01 13:53 ` Simon Horman
2024-01-30 12:08 ` [patch net-next v2 3/3] net/mlx5: DPLL, Implement lock status error value Jiri Pirko
2024-02-01 13:53 ` Simon Horman
2024-02-01 14:50 ` [patch net-next v2 0/3] dpll: expose lock status error value to user 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=20240201070241.469b0824@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.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.