All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, arkadiusz.kubalewski@intel.com,
	davem@davemloft.net, donald.hunter@gmail.com,
	edumazet@google.com, kuba@kernel.org, jiri@resnulli.us,
	mschmidt@redhat.com, pabeni@redhat.com, pvaanane@redhat.com,
	poros@redhat.com, Prathosh.Satish@microchip.com,
	horms@kernel.org, vadim.fedorenko@linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/5] dpll: add NCO pin type and zl3073x support
Date: Mon, 06 Jul 2026 12:50:14 +0000	[thread overview]
Message-ID: <178334221414.555369.260570406265552226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630125536.720717-1-ivecera@redhat.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 30 Jun 2026 14:55:31 +0200 you wrote:
> Add a new DPLL_PIN_TYPE_INT_NCO pin type for virtual pins representing
> the NCO mode of a DPLL and implement support for it in the zl3073x driver.
> 
> Patch 1 adds a STATE_CONNECTED_OVERRIDE pin capability for pins that
> can override input selection in any DPLL mode, with a WARN_ON check
> in dpll_pin_register() that STATE_CAN_CHANGE is also set.
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/5] dpll: add STATE_CONNECTED_OVERRIDE pin capability
    https://git.kernel.org/netdev/net-next/c/b1d0c412088e
  - [net-next,v6,2/5] dpll: add DPLL_PIN_TYPE_INT_NCO pin type
    https://git.kernel.org/netdev/net-next/c/0cc8348a9786
  - [net-next,v6,3/5] dpll: zl3073x: use per-operation poll timeouts
    https://git.kernel.org/netdev/net-next/c/2b11bde391c4
  - [net-next,v6,4/5] dpll: zl3073x: add per-DPLL serialization lock
    https://git.kernel.org/netdev/net-next/c/21460118d71b
  - [net-next,v6,5/5] dpll: zl3073x: add NCO virtual input pin
    https://git.kernel.org/netdev/net-next/c/3553976ffe2f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-06 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 12:55 [PATCH net-next v6 0/5] dpll: add NCO pin type and zl3073x support Ivan Vecera
2026-06-30 12:55 ` [PATCH net-next v6 1/5] dpll: add STATE_CONNECTED_OVERRIDE pin capability Ivan Vecera
2026-06-30 12:55 ` [PATCH net-next v6 2/5] dpll: add DPLL_PIN_TYPE_INT_NCO pin type Ivan Vecera
2026-07-06  9:31   ` Paolo Abeni
2026-07-06 11:47     ` Vadim Fedorenko
2026-06-30 12:55 ` [PATCH net-next v6 3/5] dpll: zl3073x: use per-operation poll timeouts Ivan Vecera
2026-07-03  9:20   ` Petr Oros
2026-06-30 12:55 ` [PATCH net-next v6 4/5] dpll: zl3073x: add per-DPLL serialization lock Ivan Vecera
2026-07-03  9:21   ` Petr Oros
2026-06-30 12:55 ` [PATCH net-next v6 5/5] dpll: zl3073x: add NCO virtual input pin Ivan Vecera
2026-07-06 12:50 ` patchwork-bot+netdevbpf [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=178334221414.555369.260570406265552226.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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=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 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.