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,
corbet@lwn.net, mschmidt@redhat.com, pabeni@redhat.com,
pvaanane@redhat.com, poros@redhat.com,
Prathosh.Satish@microchip.com, skhan@linuxfoundation.org,
horms@kernel.org, vadim.fedorenko@linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] dpll: add pin operational state
Date: Thu, 30 Apr 2026 14:30:08 +0000 [thread overview]
Message-ID: <177755940880.3033474.8176113325052727327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260428154907.2820654-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 28 Apr 2026 17:49:05 +0200 you wrote:
> Add pin operational state (operstate) to the DPLL subsystem to
> separate administrative intent from actual hardware status.
>
> Currently pin-state mixes what the user requested (connected,
> selectable, disconnected) with what the hardware is actually doing.
> This makes it difficult to diagnose situations where a user sets
> a pin as selectable or connected but the hardware cannot use it
> due to signal issues.
>
> [...]
Here is the summary with links:
- [net-next,1/2] dpll: add pin operational state
https://git.kernel.org/netdev/net-next/c/781c8893a5da
- [net-next,2/2] dpll: zl3073x: implement pin operational state reporting
https://git.kernel.org/netdev/net-next/c/c53f8f8dce77
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-30 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 15:49 [PATCH net-next 0/2] dpll: add pin operational state Ivan Vecera
2026-04-28 15:49 ` [PATCH net-next 1/2] " Ivan Vecera
2026-04-29 8:55 ` Jiri Pirko
2026-04-29 10:45 ` Vadim Fedorenko
2026-04-30 11:58 ` Petr Oros
2026-04-28 15:49 ` [PATCH net-next 2/2] dpll: zl3073x: implement pin operational state reporting Ivan Vecera
2026-04-30 11:58 ` Petr Oros
2026-04-30 14:21 ` Paolo Abeni
2026-04-30 14:30 ` 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=177755940880.3033474.8176113325052727327.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--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=pvaanane@redhat.com \
--cc=skhan@linuxfoundation.org \
--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