From: Jakub Kicinski <kuba@kernel.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] dpll: add phase-adjust-gran pin attribute
Date: Tue, 28 Oct 2025 18:39:19 -0700 [thread overview]
Message-ID: <20251028183919.785258a9@kernel.org> (raw)
In-Reply-To: <20251024144927.587097-2-ivecera@redhat.com>
On Fri, 24 Oct 2025 16:49:26 +0200 Ivan Vecera wrote:
> + -
> + name: phase-adjust-gran
> + type: s32
> + doc: |
> + Granularity of phase adjustment, in picoseconds. The value of
> + phase adjustment must be a multiple of this granularity.
Do we need this to be signed?
next prev parent reply other threads:[~2025-10-29 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 14:49 [PATCH net-next 0/2] dpll: Add support for phase adjustment granularity Ivan Vecera
2025-10-24 14:49 ` [PATCH net-next 1/2] dpll: add phase-adjust-gran pin attribute Ivan Vecera
2025-10-29 1:39 ` Jakub Kicinski [this message]
2025-10-29 7:44 ` Ivan Vecera
2025-10-29 14:20 ` Jiri Pirko
2025-10-29 15:00 ` Ivan Vecera
2025-10-29 10:20 ` Vadim Fedorenko
2025-10-29 11:17 ` Ivan Vecera
2025-10-24 14:49 ` [PATCH net-next 2/2] dpll: zl3073x: Specify phase adjustment granularity for pins Ivan Vecera
2025-10-29 1:36 ` [PATCH net-next 0/2] dpll: Add support for phase adjustment granularity Jakub Kicinski
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=20251028183919.785258a9@kernel.org \
--to=kuba@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.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=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 \
--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.