From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: David Miller <davem@redhat.com>
Cc: nicolas.ferre@atmel.com, plagnioj@jcrosoft.com,
alexandre.belloni@free-electrons.com, linux@maxim.org.za,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ARM: at91: remove phy fixup for sama5d3xek boards
Date: Wed, 2 Jul 2014 13:48:53 +0200 [thread overview]
Message-ID: <20140702134853.43d624c9@bbrezillon> (raw)
In-Reply-To: <20140701.153806.1074873302413556163.davem@redhat.com>
Hello David,
On Tue, 01 Jul 2014 15:38:06 -0700 (PDT)
David Miller <davem@redhat.com> wrote:
> From: Boris BREZILLON <boris.brezillon@free-electrons.com>
> Date: Thu, 26 Jun 2014 12:13:33 +0200
>
> > This patch removes a board specific hook for sama5d3xek boards from
> > the sama5d3 generic DT board file.
> >
> > This hook (which register a phy fixup configuring board specific
> > delays in the ksz9021 ethernet phy) is now replaced by the
> > appropriate DT properties definitions in the sama5d3xcm.dtsi file.
> >
> > Changes since v1:
> > - fix txc-skew-ps and rxc-skew-ps delays
> > - remove phy address info to handle Ronetix and Embest HW designs
>
> These patches do not apply cleanly to 'net' nor 'net-next', in fact
> you did not even say which tree these changes are targetting.
Actually, these patches were intended to be taken through at91 (and then
arm-soc) tree.
The reason I added netdev in Cc is because I wanted to get feedback on
the DT phy node definition (which I got from Florian).
I guess patch 2 does not apply cleanly because I based this work on top
of other changes which are not merged yet ([1]).
Nicolas, I'll take care to rebase this series on top of linus/master
branch (or whatever branch you want me to base it onto).
Thanks,
Boris
[1]http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/265216.html
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-02 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:13 [PATCH v2 0/2] ARM: at91: remove phy fixup for sama5d3xek boards Boris BREZILLON
2014-06-26 10:13 ` [PATCH v2 1/2] ARM: at91/dt: describe rgmii ethernet phy connected to " Boris BREZILLON
2014-06-26 18:15 ` Florian Fainelli
2014-06-26 20:01 ` Boris BREZILLON
2014-06-27 7:52 ` Nicolas Ferre
[not found] ` <20140710110720.03f437eb@bbrezillon>
2014-07-10 15:35 ` Florian Fainelli
2014-07-10 17:19 ` Boris BREZILLON
2014-07-10 17:46 ` Florian Fainelli
[not found] ` <CAGVrzcawPiJgQF-=18ZvFGr3LhZgS1ZSZMYA3i5x874S6=jcXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-10 19:32 ` Boris BREZILLON
2014-06-26 10:13 ` [PATCH v2 2/2] ARM: at91: remove phy fixup for " Boris BREZILLON
2014-07-01 22:38 ` [PATCH v2 0/2] " David Miller
2014-07-02 11:48 ` Boris BREZILLON [this message]
2014-07-09 16:34 ` Boris BREZILLON
2014-07-10 2:24 ` Bo Shen
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=20140702134853.43d624c9@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=davem@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
/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).