mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, poros@redhat.com,
	arkadiusz.kubalewski@intel.com, davem@davemloft.net,
	donald.hunter@gmail.com, edumazet@google.com, jiri@resnulli.us,
	mschmidt@redhat.com, pabeni@redhat.com, pvaanane@redhat.com,
	Prathosh.Satish@microchip.com, horms@kernel.org,
	vadim.fedorenko@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] dpll: zl3073x: add NCO virtual input pin
Date: Sun, 24 May 2026 17:54:43 +0200	[thread overview]
Message-ID: <e928da41-90f1-4e7b-ac43-4440c3b91335@redhat.com> (raw)
In-Reply-To: <20260523002742.1766902-1-kuba@kernel.org>

Hi Kuba,

On 5/23/26 2:27 AM, Jakub Kicinski wrote:
> This is an AI-generated review of your patch. The human sending this
> email says "I think the report / question about the SEM wasn't asked
> on v2?"

I see some potential locking issues besides Sashiko findings... I have
planned to include the locking change in zl3073x in PTP series but
IMHO it will be better to include it here.

Thanks,
Ivan


      reply	other threads:[~2026-05-24 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  7:42 [PATCH net-next v3 0/2] dpll: add NCO pin type and zl3073x support Ivan Vecera
2026-05-21  7:42 ` [PATCH net-next v3 1/2] dpll: add DPLL_PIN_TYPE_INT_NCO pin type Ivan Vecera
2026-05-21  7:42 ` [PATCH net-next v3 2/2] dpll: zl3073x: add NCO virtual input pin Ivan Vecera
2026-05-23  0:27   ` Jakub Kicinski
2026-05-24 15:54     ` Ivan Vecera [this message]

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=e928da41-90f1-4e7b-ac43-4440c3b91335@redhat.com \
    --to=ivecera@redhat.com \
    --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=jiri@resnulli.us \
    --cc=kuba@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=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
all inboxes | Powered by JetHome®