From: Tao Ren <rentao.bupt@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, olteanv@gmail.com,
arun.parameswaran@broadcom.com, justinpopo6@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH net-next v10 0/3] net: phy: support 1000Base-X auto-negotiation for BCM54616S
Date: Wed, 23 Oct 2019 23:29:03 -0700 [thread overview]
Message-ID: <20191024062902.GA52817@taoren-ubuntuvm> (raw)
In-Reply-To: <20191023.204311.1181447784152558295.davem@davemloft.net>
On Wed, Oct 23, 2019 at 08:43:11PM -0700, David Miller wrote:
> From: rentao.bupt@gmail.com
> Date: Tue, 22 Oct 2019 11:31:05 -0700
>
> > From: Tao Ren <rentao.bupt@gmail.com>
> >
> > This patch series aims at supporting auto negotiation when BCM54616S is
> > running in 1000Base-X mode: without the patch series, BCM54616S PHY driver
> > would report incorrect link speed in 1000Base-X mode.
> >
> > Patch #1 (of 3) modifies assignment to OR when dealing with dev_flags in
> > phy_attach_direct function, so that dev_flags updated in BCM54616S PHY's
> > probe callback won't be lost.
> >
> > Patch #2 (of 3) adds several genphy_c37_* functions to support clause 37
> > 1000Base-X auto-negotiation, and these functions are called in BCM54616S
> > PHY driver.
> >
> > Patch #3 (of 3) detects BCM54616S PHY's operation mode and calls according
> > genphy_c37_* functions to configure auto-negotiation and parse link
> > attributes (speed, duplex, and etc.) in 1000Base-X mode.
>
> Series applied to net-next, thank you.
Great. Thank you David!
Cheers,
Tao
prev parent reply other threads:[~2019-10-24 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 18:31 [PATCH net-next v10 0/3] net: phy: support 1000Base-X auto-negotiation for BCM54616S rentao.bupt
2019-10-22 18:31 ` [PATCH net-next v10 1/3] net: phy: modify assignment to OR for dev_flags in phy_attach_direct rentao.bupt
2019-10-22 18:31 ` [PATCH net-next v10 2/3] net: phy: add support for clause 37 auto-negotiation rentao.bupt
2019-10-22 18:31 ` [PATCH net-next v10 3/3] net: phy: broadcom: add 1000Base-X support for BCM54616S rentao.bupt
2019-10-24 3:43 ` [PATCH net-next v10 0/3] net: phy: support 1000Base-X auto-negotiation " David Miller
2019-10-24 6:29 ` Tao Ren [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=20191024062902.GA52817@taoren-ubuntuvm \
--to=rentao.bupt@gmail.com \
--cc=andrew@lunn.ch \
--cc=arun.parameswaran@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=justinpopo6@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=openbmc@lists.ozlabs.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