From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next v2 1/4] enetc: Clean up MAC and link configuration
Date: Wed, 7 Oct 2020 10:55:31 +0000 [thread overview]
Message-ID: <20201007105530.b4kdnhgzrnpfdoa2@skbuf> (raw)
In-Reply-To: <20201007094823.6960-2-claudiu.manoil@nxp.com>
On Wed, Oct 07, 2020 at 12:48:20PM +0300, Claudiu Manoil wrote:
> Decouple level MAC configuration based on phy interface type
> from general port configuration.
> Group together MAC and link configuration code.
> Decouple external mdio bus creation from interface type
> parsing. No longer return an (unhandled) error code when
> phy_node not found, use phy_node to indicate whether the
> port has a phy or not. No longer fall-through when serdes
> configuration fails for the link modes that require
> internal link configuration.
>
> Signed-off-by: Claudiu Manoil <claudiu.manoil@nxp.com>
Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
next prev parent reply other threads:[~2020-10-07 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 9:48 [PATCH net-next v2 0/4] enetc: Migrate to PHYLINK and PCS_LYNX Claudiu Manoil
2020-10-07 9:48 ` [PATCH net-next v2 1/4] enetc: Clean up MAC and link configuration Claudiu Manoil
2020-10-07 10:55 ` Ioana Ciornei [this message]
2020-10-07 9:48 ` [PATCH net-next v2 2/4] enetc: Clean up serdes configuration Claudiu Manoil
2020-10-07 10:56 ` Ioana Ciornei
2020-10-07 9:48 ` [PATCH net-next v2 3/4] arm64: dts: fsl-ls1028a-rdb: Specify in-band mode for ENETC port 0 Claudiu Manoil
2020-10-07 10:31 ` Vladimir Oltean
2020-10-07 9:48 ` [PATCH net-next v2 4/4] enetc: Migrate to PHYLINK and PCS_LYNX Claudiu Manoil
2020-10-07 10:54 ` Ioana Ciornei
2020-10-11 18:08 ` [PATCH net-next v2 0/4] " Jakub Kicinski
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=20201007105530.b4kdnhgzrnpfdoa2@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox