From: Randy Dunlap <rdunlap@infradead.org>
To: Stefan Wahren <wahrenst@gmx.net>,
Parthiban Veerasooran <parthiban.veerasooran@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: oa-tc6-framework: Fix link to specification
Date: Tue, 18 Aug 2026 07:51:01 -0700 [thread overview]
Message-ID: <1aa6cc61-cc55-4186-91f7-e072af4e1975@infradead.org> (raw)
In-Reply-To: <20260818135958.17311-1-wahrenst@gmx.net>
On 8/18/26 6:59 AM, Stefan Wahren wrote:
> Current link for 10BASE-T1x MAC-PHY Serial Interface Specification
> doesn't work - it returns 404. Update the link to the working one.
>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/networking/oa-tc6-framework.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/oa-tc6-framework.rst b/Documentation/networking/oa-tc6-framework.rst
> index 013824078cea..0feda2f9d840 100644
> --- a/Documentation/networking/oa-tc6-framework.rst
> +++ b/Documentation/networking/oa-tc6-framework.rst
> @@ -77,7 +77,7 @@ Reference
>
> 10BASE-T1x MAC-PHY Serial Interface Specification,
>
> -Link: https://opensig.org/download/document/OPEN_Alliance_10BASET1x_MAC-PHY_Serial_Interface_V1.1.pdf
> +Link: https://opensig.org/wp-content/uploads/2023/12/OPEN_Alliance_10BASET1x_MAC-PHY_Serial_Interface_V1.1.pdf
>
> Hardware Architecture
> ---------------------
--
~Randy
next prev parent reply other threads:[~2026-08-18 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 13:59 [PATCH] docs: oa-tc6-framework: Fix link to specification Stefan Wahren
2026-08-18 14:51 ` Randy Dunlap [this message]
2026-08-20 20:40 ` patchwork-bot+netdevbpf
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=1aa6cc61-cc55-4186-91f7-e072af4e1975@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parthiban.veerasooran@microchip.com \
--cc=skhan@linuxfoundation.org \
--cc=wahrenst@gmx.net \
/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.