From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Ivan Vecera <ivecera@redhat.com>, netdev@vger.kernel.org
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
Donald Hunter <donald.hunter@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>
Subject: Re: [PATCH net-next v2 1/3] dpll: add phase-offset-avg-factor device attribute to netlink spec
Date: Sat, 27 Sep 2025 15:09:27 +0100 [thread overview]
Message-ID: <5cb17e65-bda4-4ec8-90bb-4d8203a51557@linux.dev> (raw)
In-Reply-To: <20250927084912.2343597-2-ivecera@redhat.com>
On 27/09/2025 09:49, Ivan Vecera wrote:
> Add dpll device level attribute DPLL_A_PHASE_OFFSET_AVG_FACTOR to allow
> control over a calculation of reported phase offset value. Attribute is
> present, if the driver provides such capability, otherwise attribute
> shall not be present.
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-09-27 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 8:49 [PATCH net-next v2 0/3] dpll: add phase offset averaging factor Ivan Vecera
2025-09-27 8:49 ` [PATCH net-next v2 1/3] dpll: add phase-offset-avg-factor device attribute to netlink spec Ivan Vecera
2025-09-27 14:09 ` Vadim Fedorenko [this message]
2025-09-27 8:49 ` [PATCH net-next v2 2/3] dpll: add phase_offset_avg_factor_get/set callback ops Ivan Vecera
2025-09-27 8:49 ` [PATCH net-next v2 3/3] dpll: zl3073x: Allow to configure phase offset averaging factor Ivan Vecera
2025-09-27 22:52 ` [PATCH net-next v2 0/3] dpll: add " Vadim Fedorenko
2025-09-30 2:30 ` 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=5cb17e65-bda4-4ec8-90bb-4d8203a51557@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.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 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.