public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	netdev@vger.kernel.org, robin.murphy@arm.com,
	marc.zyngier@arm.com, afaerber@suse.de, bert@a20.net,
	linux-sunxi@googlegroups.com, maxime.ripard@free-electrons.com,
	Gabriel Fernandez <gabriel.fernandez@linaro.org>,
	Dinh Nguyen <dinh.linux@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Phil Reid <preid@electromag.com.au>
Subject: Re: [PATCH 2/2 (linux-stable-4.5.y)] stmmac: fix MDIO settings
Date: Sun, 14 Aug 2016 17:44:41 +0200	[thread overview]
Message-ID: <20160814154441.GJ20560@kroah.com> (raw)
In-Reply-To: <1464009463-23654-3-git-send-email-peppe.cavallaro@st.com>

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@st.com>
> Reviewed-by: Andreas F�rber <afaerber@suse.de>
> Tested-by: Frank Sch�fer <fschaefer.oss@googlemail.com>
> Cc: Gabriel Fernandez <gabriel.fernandez@linaro.org>
> Cc: Dinh Nguyen <dinh.linux@gmail.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Phil Reid <preid@electromag.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>

  reply	other threads:[~2016-08-14 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 13:17 [PATCH 0/2 (linux-stable-4.5.y)] net: stmmac: MDIO fixes Giuseppe Cavallaro
2016-05-23 13:17 ` [PATCH 1/2 (linux-stable-4.5.y)] Revert "stmmac: Fix 'eth0: No PHY found' regression" Giuseppe Cavallaro
2016-08-14 15:44   ` Greg KH
2016-05-23 13:17 ` [PATCH 2/2 (linux-stable-4.5.y)] stmmac: fix MDIO settings Giuseppe Cavallaro
2016-08-14 15:44   ` Greg KH [this message]
2016-05-23 15:36 ` [PATCH 0/2 (linux-stable-4.5.y)] net: stmmac: MDIO fixes Greg KH
2016-05-24  7:08   ` Giuseppe CAVALLARO

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=20160814154441.GJ20560@kroah.com \
    --to=greg@kroah.com \
    --cc=afaerber@suse.de \
    --cc=bert@a20.net \
    --cc=davem@davemloft.net \
    --cc=dinh.linux@gmail.com \
    --cc=gabriel.fernandez@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=marc.zyngier@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=preid@electromag.com.au \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.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