From: Henri Roosen <henri.roosen@ginzinger.com>
To: David Miller <davem@davemloft.net>, <andrew@lunn.ch>
Cc: <f.fainelli@gmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] phy: micrel: Fix finding PHY properties in MAC node for KSZ9031.
Date: Wed, 23 Dec 2015 09:42:24 +0100 [thread overview]
Message-ID: <567A5E70.1010407@ginzinger.com> (raw)
In-Reply-To: <20151222.171444.1073714139867888727.davem@davemloft.net>
On 12/22/2015 11:14 PM, David Miller wrote:
> From: Andrew Lunn <andrew@lunn.ch>
> Date: Tue, 22 Dec 2015 12:06:34 +0100
>
>> On Tue, Dec 22, 2015 at 11:58:40AM +0100, Henri Roosen wrote:
>>> Commit 651df2183543 ("phy: micrel: Fix finding PHY properties in MAC
>>> node.") only fixes finding PHY properties in MAC node for KSZ9021. This
>>> commit applies the same fix for KSZ9031.
>>>
>>> Signed-off-by: Henri Roosen <henri.roosen@ginzinger.com>
>>
>> Fixes: 8b63ec1837fa ("phylib: Make PHYs children of their MDIO bus, not the bus' parent.")
>>
>> Acked-by: Andrew Lunn <andrew@lunn.ch>
>
> This does not apply cleanly to any of my trees.
Found the problem. It's the mail server. Will send a correct patch later.
>
________________________________
Ginzinger electronic systems GmbH
Gewerbegebiet Pirath 16
4952 Weng im Innkreis
www.ginzinger.com
Firmenbuchnummer: FN 364958d
Firmenbuchgericht: Ried im Innkreis
UID-Nr.: ATU66521089
________________________________
*** WEIHNACHTSURLAUB VON DONNERSTAG, DEN 24. DEZEMBER 2015 BIS MITTWOCH, DEN 6. JAENNER 2016 ***
*** CHRISTMAS VACATION FROM THURSDAY, THE 24 DECEMBER 2015 TO WEDNESDAY, 6 JANUARY 2016 ***
prev parent reply other threads:[~2015-12-23 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 10:58 [PATCH 1/1] phy: micrel: Fix finding PHY properties in MAC node for KSZ9031 Henri Roosen
2015-12-22 11:06 ` Andrew Lunn
2015-12-22 22:14 ` David Miller
2015-12-23 8:11 ` Henri Roosen
2015-12-23 16:37 ` David Miller
2015-12-23 8:42 ` Henri Roosen [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=567A5E70.1010407@ginzinger.com \
--to=henri.roosen@ginzinger.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).