From: Jakub Kicinski <kuba@kernel.org>
To: ivecera@redhat.com
Cc: netdev@vger.kernel.org, poros@redhat.com,
vadim.fedorenko@linux.dev, Chris.duQuesnay@microchip.com,
arkadiusz.kubalewski@intel.com, jiri@resnulli.us,
min.li@microchip.com, pabeni@redhat.com,
richardcochran@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v8 2/3] dpll: zl3073x: add channel ToD, phase step and TIE operations
Date: Tue, 18 Aug 2026 09:51:54 -0700 [thread overview]
Message-ID: <20260818095154.43f79293@kernel.org> (raw)
In-Reply-To: <20260818163746.3988829-1-kuba@kernel.org>
On Tue, 18 Aug 2026 09:37:46 -0700 Jakub Kicinski wrote:
> This is an AI-generated review of your patch. The human sending this
> email has considered the AI review valid, or at least plausible.
Ignore, got confused between feedback on patches 2 and 3 and thought
you(r LLM) were just responding to Gemi-shiko.
next prev parent reply other threads:[~2026-08-18 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 8:26 [PATCH net-next v8 0/3] dpll: zl3073x: add PTP clock support Ivan Vecera
2026-08-14 8:26 ` [PATCH net-next v8 1/3] dpll: zl3073x: scale poll interval proportionally to timeout Ivan Vecera
2026-08-14 8:26 ` [PATCH net-next v8 2/3] dpll: zl3073x: add channel ToD, phase step and TIE operations Ivan Vecera
2026-08-16 14:47 ` Ivan Vecera
2026-08-18 16:37 ` Jakub Kicinski
2026-08-18 16:51 ` Jakub Kicinski [this message]
2026-08-14 8:26 ` [PATCH net-next v8 3/3] dpll: zl3073x: add PTP clock support Ivan Vecera
2026-08-16 14:52 ` Ivan Vecera
2026-08-18 16:37 ` Jakub Kicinski
2026-08-18 17:00 ` [PATCH net-next v8 0/3] " 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=20260818095154.43f79293@kernel.org \
--to=kuba@kernel.org \
--cc=Chris.duQuesnay@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=richardcochran@gmail.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.