From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "Martin Hundebøll" <mnhu@prevas.dk>, netdev <netdev@vger.kernel.org>
Subject: Re: [net-next] dsa: slave: support phy devices on external MII bus
Date: Wed, 18 Oct 2017 21:31:45 +0200 [thread overview]
Message-ID: <20171018193145.GK15371@lunn.ch> (raw)
In-Reply-To: <2e120f66-eb0b-7bfe-450c-db061defca09@gmail.com>
> I guess, thanks for making me post this example and realize this is
> probably no longer necessary :)
Hi Florian
You are welcome. Please test and report back. This code is complex, so
removing part of it would be great.
Andrew
prev parent reply other threads:[~2017-10-18 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 16:21 [net-next] dsa: slave: support phy devices on external MII bus Andrew Lunn
2017-10-18 16:51 ` Florian Fainelli
2017-10-18 17:30 ` Martin Hundebøll
2017-10-18 18:54 ` Florian Fainelli
2017-10-18 19:09 ` Andrew Lunn
2017-10-18 19:18 ` Florian Fainelli
2017-10-18 19:31 ` Andrew Lunn [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=20171018193145.GK15371@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=mnhu@prevas.dk \
--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).