From: Jakub Kicinski <kuba@kernel.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Donald Hunter <donald.hunter@gmail.com>,
Eric Dumazet <edumazet@google.com>, Jiri Pirko <jiri@resnulli.us>,
Michal Schmidt <mschmidt@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Pasi Vaananen <pvaanane@redhat.com>, Petr Oros <poros@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Simon Horman <horms@kernel.org>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] dpll: add DPLL_PIN_TYPE_INT_NCO pin type
Date: Wed, 20 May 2026 19:16:31 -0700 [thread overview]
Message-ID: <20260520191631.639a9820@kernel.org> (raw)
In-Reply-To: <20260516175744.26749-2-ivecera@redhat.com>
On Sat, 16 May 2026 19:57:43 +0200 Ivan Vecera wrote:
> ---
> v2:
> - Clarify int-nco pin type documentation to describe frequency
> control via the PTP clock interface instead of generic "controlled
> by the host".
> - Tighten FFO attribute documentation for INT_NCO pins to describe
> the DPLL's output frequency offset from nominal frequency.
> - Mention both fractional-frequency-offset (PPM) and
> fractional-frequency-offset-ppt attributes in the commit message.
>
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
Both patches have SoB after --- and changelog, please fix :(
next prev parent reply other threads:[~2026-05-21 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 17:57 [PATCH net-next v2 0/2] dpll: add NCO pin type and zl3073x support Ivan Vecera
2026-05-16 17:57 ` [PATCH net-next v2 1/2] dpll: add DPLL_PIN_TYPE_INT_NCO pin type Ivan Vecera
2026-05-17 8:19 ` Jiri Pirko
2026-05-21 2:16 ` Jakub Kicinski [this message]
2026-05-16 17:57 ` [PATCH net-next v2 2/2] dpll: zl3073x: add NCO virtual input pin Ivan Vecera
2026-05-19 17:57 ` Petr Oros
2026-05-20 8:58 ` Ivan Vecera
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=20260520191631.639a9820@kernel.org \
--to=kuba@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--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-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=pvaanane@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox