Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, poros@redhat.com,
	dsahern@kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next] ip: display DPLL pin information in link details
Date: Wed, 15 Jul 2026 15:20:05 +0000	[thread overview]
Message-ID: <178412880565.4127287.3287584044929138457.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260713092119.1536385-1-ivecera@redhat.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Mon, 13 Jul 2026 11:21:19 +0200 you wrote:
> Parse the IFLA_DPLL_PIN nested attribute and display the associated
> DPLL pin ID in 'ip link show' detail output. This allows users to see
> which DPLL recovered clock pin is associated with a network interface
> without having to cross-reference with 'dpll pin show'.
> 
> Example output:
>   $ ip -d link show eth0
>   ... parentbus pci parentdev 0000:51:00.0 dpll-pin 4
> 
> [...]

Here is the summary with links:
  - [iproute2-next] ip: display DPLL pin information in link details
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=20e860c632e3

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



      reply	other threads:[~2026-07-15 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  9:21 [PATCH iproute2-next] ip: display DPLL pin information in link details Ivan Vecera
2026-07-15 15:20 ` 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=178412880565.4127287.3287584044929138457.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=poros@redhat.com \
    --cc=stephen@networkplumber.org \
    /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