From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: linux@armlinux.org.uk, f.fainelli@gmail.com, andrew@lunn.ch,
hkallweit1@gmail.com, olteanv@gmail.com,
thomas.petazzoni@bootlin.com, davem@davemloft.net,
vivien.didelot@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 06/11] net: phylink: Add struct phylink_config to PHYLINK API
Date: Wed, 29 May 2019 09:28:45 +0200 [thread overview]
Message-ID: <20190529092845.4bc7439f@bootlin.com> (raw)
In-Reply-To: <1559065097-31832-7-git-send-email-ioana.ciornei@nxp.com>
Hello Ioana,
On Tue, 28 May 2019 20:38:12 +0300
Ioana Ciornei <ioana.ciornei@nxp.com> wrote:
>The phylink_config structure will encapsulate a pointer to a struct
>device and the operation type requested for this instance of PHYLINK.
>This patch does not make any functional changes, it just transitions the
>PHYLINK internals and all its users to the new API.
>
>A pointer to a phylink_config structure will be passed to
>phylink_create() instead of the net_device directly. Also, the same
>phylink_config pointer will be passed back to all phylink_mac_ops
>callbacks instead of the net_device. Using this mechanism, a PHYLINK
>user can get the original net_device using a structure such as
>'to_net_dev(config->dev)' or directly the structure containing the
>phylink_config using a container_of call.
I see that you mixed both to_net_dev and container_of uses in mvpp2, is
there a reason for that ?
Other than that, for the mvpp2 part,
Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Tested-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Thanks,
Maxime
next prev parent reply other threads:[~2019-05-29 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 17:38 [PATCH v2 net-next 00/11] Decoupling PHYLINK from struct net_device Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 01/11] net: phy: Add phy_sysfs_create_links helper function Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 02/11] net: phy: Guard against the presence of a netdev Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 03/11] net: phy: Check against net_device being NULL Ioana Ciornei
2019-05-28 17:57 ` Florian Fainelli
2019-05-28 17:38 ` [PATCH v2 net-next 04/11] net: phy: Add phy_standalone sysfs entry Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 05/11] net: phylink: Add phylink_mac_link_{up,down} wrapper functions Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 06/11] net: phylink: Add struct phylink_config to PHYLINK API Ioana Ciornei
2019-05-29 7:28 ` Maxime Chevallier [this message]
2019-05-29 16:18 ` Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 07/11] net: phylink: Add PHYLINK_DEV operation type Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 08/11] net: phylink: Add phylink_{printk,err,warn,info,dbg} macros Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 09/11] net: dsa: Move the phylink driver calls into port.c Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 10/11] net: dsa: Use PHYLINK for the CPU/DSA ports Ioana Ciornei
2019-05-28 17:38 ` [PATCH v2 net-next 11/11] net: dsa: sja1105: Fix broken fixed-link interfaces on user ports Ioana Ciornei
2019-05-30 4:49 ` [PATCH v2 net-next 00/11] Decoupling PHYLINK from struct net_device David Miller
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=20190529092845.4bc7439f@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vivien.didelot@gmail.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.