All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	fvdw@fvdw.eu, gregory.clement@free-electrons.com
Subject: Re: [PATCH] ARM: orion: Fix DSA platform device after mvmdio conversion
Date: Fri, 06 Nov 2015 13:18:53 -0800	[thread overview]
Message-ID: <563D193D.7070400@gmail.com> (raw)
In-Reply-To: <20151106193717.GA9437@kroah.com>

On 06/11/15 11:37, Greg KH wrote:
> On Fri, Nov 06, 2015 at 11:31:30AM -0800, Florian Fainelli wrote:
>> DSA expects the mii_bus pointer to be the device structure associated
>> with the MDIO bus controller driver. First commit breaking that was
>> c3a07134e6aa ("mv643xx_eth: convert to use the Marvell Orion MDIO
>> driver"), and then, it got completely under the radar for a while.
>>
>> Reported-by: Frans van de Wiel <fvdw@fvdw.eu>
>> Fixes: c3a07134e6aa ("mv643xx_eth: convert to use the Marvell Orion MDIO driver")
>> CC: stable@vger.kernel.org
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> Greg,
>>
>> This is the patch for kernels 3.10 through 3.17, thanks!
> 
> What is the git commit id of this in Linus's tree?
>

Upstream commit is d836ace65ee98d7079bc3c5afdbcc0e27dca20a3 ("ARM:
orion: Fix DSA platform device after mvmdio conversion").
-- 
Florian

      reply	other threads:[~2015-11-06 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  5:54 Patch "ARM: orion: Fix DSA platform device after mvmdio conversion" has been added to the 4.2-stable tree gregkh
2015-11-06 19:31 ` [PATCH] ARM: orion: Fix DSA platform device after mvmdio conversion Florian Fainelli
2015-11-06 19:37   ` Greg KH
2015-11-06 21:18     ` Florian Fainelli [this message]

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=563D193D.7070400@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=fvdw@fvdw.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.