[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160814154441.GJ20560@kroah.com>
Date: Sun, 14 Aug 2016 17:44:41 +0200
From: Greg KH <greg@...ah.com>
To: Giuseppe Cavallaro <peppe.cavallaro@...com>
Cc: stable@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev@...r.kernel.org, robin.murphy@....com, marc.zyngier@....com,
afaerber@...e.de, bert@....net, linux-sunxi@...glegroups.com,
maxime.ripard@...e-electrons.com,
Gabriel Fernandez <gabriel.fernandez@...aro.org>,
Dinh Nguyen <dinh.linux@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Phil Reid <preid@...ctromag.com.au>
Subject: Re: [PATCH 2/2 (linux-stable-4.5.y)] stmmac: fix MDIO settings
On Mon, May 23, 2016 at 03:17:43PM +0200, Giuseppe Cavallaro wrote:
> Initially the phy_bus_name was added to manipulate the
> driver name but it was recently just used to manage the
> fixed-link and then to take some decision at run-time.
> So the patch uses the is_pseudo_fixed_link and removes
> the phy_bus_name variable not necessary anymore.
>
> The driver can manage the mdio registration by using phy-handle,
> dwmac-mdio and own parameter e.g. snps,phy-addr.
> This patch takes care about all these possible configurations
> and fixes the mdio registration in case of there is a real
> transceiver or a switch (that needs to be managed by using
> fixed-link).
>
> Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@...com>
> Reviewed-by: Andreas Färber <afaerber@...e.de>
> Tested-by: Frank Schäfer <fschaefer.oss@...glemail.com>
> Cc: Gabriel Fernandez <gabriel.fernandez@...aro.org>
> Cc: Dinh Nguyen <dinh.linux@...il.com>
> Cc: David S. Miller <davem@...emloft.net>
> Cc: Phil Reid <preid@...ctromag.com.au>
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 11 +--
> drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c | 19 +----
> .../net/ethernet/stmicro/stmmac/stmmac_platform.c | 84 +++++++++++++++++-----
> 3 files changed, 70 insertions(+), 44 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
Powered by blists - more mailing lists