From: Jakub Kicinski <kuba@kernel.org>
To: javen <javen_xu@realsil.com.cn>
Cc: <hkallweit1@gmail.com>, <nic_swsd@realtek.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<maxime.chevallier@bootlin.com>, <horms@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 0/7] r8169: add support for phylink
Date: Mon, 29 Jun 2026 16:07:50 -0700 [thread overview]
Message-ID: <20260629160750.0a84e5e8@kernel.org> (raw)
In-Reply-To: <20260629060931.1006-1-javen_xu@realsil.com.cn>
On Mon, 29 Jun 2026 14:09:24 +0800 javen wrote:
> This series patch adds support for phylink. RTL8116af is a fiber mode
> card, link status and speed can not be read from standard phy reg. So
> we read link status and speed from serdes reg by pcs. So as RTL8127atf.
Sorry, but net-next was still closed when you posted.
It'd be unfair towards those who follow the announcements to consider
this posting, you'll have to resend.
--
pw-bot: defer
prev parent reply other threads:[~2026-06-29 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:09 [PATCH net-next v3 0/7] r8169: add support for phylink javen
2026-06-29 6:09 ` [PATCH net-next v3 1/7] r8169: add speed in private struct javen
2026-06-29 6:09 ` [PATCH net-next v3 2/7] r8169: create a virtual interrupt for linkchg javen
2026-06-29 6:09 ` [PATCH net-next v3 3/7] r8169: add support for phylink javen
2026-06-29 6:09 ` [PATCH net-next v3 4/7] r8169: add support for RTL8116af javen
2026-06-29 6:09 ` [PATCH net-next v3 5/7] r8169: add ltr " javen
2026-06-29 6:09 ` [PATCH net-next v3 6/7] r8169: fix RTL8116af can not enter s0idle and c10 javen
2026-06-29 6:09 ` [PATCH net-next v3 7/7] r8169: add phylink support for RTL8127atf javen
2026-06-29 23:07 ` Jakub Kicinski [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=20260629160750.0a84e5e8@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
/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.