From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] net: fec: fix MDIO bus assignement for dual fec SoC's
Date: Tue, 13 Jan 2015 19:42:55 +0800 [thread overview]
Message-ID: <20150113114253.GC19355@dragon> (raw)
In-Reply-To: <c9a7077c1f800f5a56ef53cd721e73f6@agner.ch>
On Mon, Jan 12, 2015 at 09:47:44AM +0100, Stefan Agner wrote:
> On 2015-01-12 03:45, fugang.duan at freescale.com wrote:
> > In additional, it is better to split the patch to two part with dts
> > and driver part.
>
> Hm, this would mandate to have the device tree with the MDIO/phy-handle
> changes merged before the net changes to maintain bisect-ability.
>
> @Dave/Shawn, what do you prefer?
I'm fine with dts change in the driver patch, if we have a good reason
for doing that.
Shawn
prev parent reply other threads:[~2015-01-13 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 14:01 [PATCH v2] net: fec: fix MDIO bus assignement for dual fec SoC's Stefan Agner
2015-01-09 16:19 ` Sascha Hauer
2015-01-12 2:45 ` fugang.duan at freescale.com
2015-01-12 8:47 ` Stefan Agner
2015-01-13 11:42 ` Shawn Guo [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=20150113114253.GC19355@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).