From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, f.fainelli@gmail.com,
maxime.chevallier@bootlin.com, kory.maincent@bootlin.com,
lukma@denx.de, corbet@lwn.net, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@armlinux.org.uk, Divya.Koppera@microchip.com
Subject: Re: [PATCH net-next v3 1/1] Documentation: networking: add Twisted Pair Ethernet diagnostics at OSI Layer 1
Date: Tue, 08 Oct 2024 09:50:30 +0000 [thread overview]
Message-ID: <172838103051.472898.7922396138133362766.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241004121824.1716303-1-o.rempel@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 4 Oct 2024 14:18:24 +0200 you wrote:
> This patch introduces a diagnostic guide for troubleshooting Twisted
> Pair Ethernet variants at OSI Layer 1. It provides detailed steps for
> detecting and resolving common link issues, such as incorrect wiring,
> cable damage, and power delivery problems. The guide also includes
> interface verification steps and PHY-specific diagnostics.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
>
> [...]
Here is the summary with links:
- [net-next,v3,1/1] Documentation: networking: add Twisted Pair Ethernet diagnostics at OSI Layer 1
https://git.kernel.org/netdev/net-next/c/e793b86ae44e
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:[~2024-10-08 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:18 Oleksij Rempel
2024-10-08 9:44 ` Paolo Abeni
2024-10-08 9: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=172838103051.472898.7922396138133362766.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®