From: Florian Fainelli <f.fainelli@gmail.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next 2/5] net: dsa: use slave device phydev
Date: Tue, 26 Sep 2017 16:54:09 -0700 [thread overview]
Message-ID: <292b4fbf-36c6-e63b-58dc-942ca71cc704@gmail.com> (raw)
In-Reply-To: <20170926211535.21273-3-vivien.didelot@savoirfairelinux.com>
On 09/26/2017 02:15 PM, Vivien Didelot wrote:
> There is no need to store a phy_device in dsa_slave_priv since
> net_device already provides one. Simply s/p->phy/dev->phydev/.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2017-09-26 23:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 21:15 [PATCH net-next 0/5] net: dsa: use generic slave phydev Vivien Didelot
2017-09-26 21:15 ` [PATCH net-next 1/5] net: dsa: return -ENODEV is there is no slave PHY Vivien Didelot
2017-09-26 21:49 ` Andrew Lunn
2017-09-26 21:59 ` Florian Fainelli
2017-09-26 21:15 ` [PATCH net-next 2/5] net: dsa: use slave device phydev Vivien Didelot
2017-09-26 21:56 ` Andrew Lunn
2017-09-26 23:54 ` Florian Fainelli [this message]
2017-09-26 21:15 ` [PATCH net-next 3/5] net: dsa: use phy_ethtool_get_link_ksettings Vivien Didelot
2017-09-26 21:57 ` Andrew Lunn
2017-09-26 22:00 ` Florian Fainelli
2017-09-26 21:15 ` [PATCH net-next 4/5] net: dsa: use phy_ethtool_set_link_ksettings Vivien Didelot
2017-09-26 21:57 ` Andrew Lunn
2017-09-26 22:05 ` Florian Fainelli
2017-09-26 21:15 ` [PATCH net-next 5/5] net: dsa: use phy_ethtool_nway_reset Vivien Didelot
2017-09-26 21:58 ` Andrew Lunn
2017-09-26 22:05 ` Florian Fainelli
2017-09-26 23:55 ` [PATCH net-next 0/5] net: dsa: use generic slave phydev Florian Fainelli
2017-09-27 3:06 ` 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=292b4fbf-36c6-e63b-58dc-942ca71cc704@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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.