From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: mvebu: add a clock for mdio nodes on Armada 370/38x/XP
Date: Mon, 7 Apr 2014 13:00:42 -0400 [thread overview]
Message-ID: <20140407170042.GI28334@titan.lakedaemon.net> (raw)
In-Reply-To: <1395790439-21332-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Wed, Mar 26, 2014 at 12:33:57AM +0100, Thomas Petazzoni wrote:
> Jason, Andrew, Gregory, Sebastian,
>
> Here is a set of two patches that add a clock specification to the
> mdio node on Armada 370/XP and Armada 38x. This allows the mvmdio
> driver to work properly when loaded as a module, before mvneta is
> loaded.
>
> I've separated the Armada 370/XP and Armada 38x fixes in two patches,
> because the Armada 370/XP fix should be pushed to stable, while the
> Armada 38x does not need to be pushed to stable since Armada 38x
> support only appears in 3.15.
>
> Thanks,
>
> Thomas
>
> Thomas Petazzoni (2):
> ARM: mvebu: ensure the mdio node has a clock reference on Armada
> 370/XP
> ARM: mvebu: ensure the mdio node has a clock reference on Armada 38x
>
> arch/arm/boot/dts/armada-370-xp.dtsi | 1 +
> arch/arm/boot/dts/armada-38x.dtsi | 1 +
> 2 files changed, 2 insertions(+)
Applied both to mvebu/dt-fixes-non-critical for v3.15. Updated for-next
as well. If all goes well, I'll send a pull request later in the week.
thx,
Jason.
prev parent reply other threads:[~2014-04-07 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 23:33 [PATCH 0/2] ARM: mvebu: add a clock for mdio nodes on Armada 370/38x/XP Thomas Petazzoni
2014-03-25 23:33 ` [PATCH 1/2] ARM: mvebu: ensure the mdio node has a clock reference on Armada 370/XP Thomas Petazzoni
2014-03-25 23:33 ` [PATCH 2/2] ARM: mvebu: ensure the mdio node has a clock reference on Armada 38x Thomas Petazzoni
2014-03-26 9:05 ` [PATCH 0/2] ARM: mvebu: add a clock for mdio nodes on Armada 370/38x/XP Andrew Lunn
2014-03-26 9:09 ` Gregory CLEMENT
2014-04-07 17:00 ` Jason Cooper [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=20140407170042.GI28334@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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 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.