From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: mvebu: Add required ethernet muxing for the Armada 370 SoC
Date: Sat, 9 Aug 2014 17:19:02 +0200 [thread overview]
Message-ID: <20140809171902.7b5d45cc@free-electrons.com> (raw)
In-Reply-To: <1407511136-26477-2-git-send-email-ezequiel.garcia@free-electrons.com>
Dear Ezequiel Garcia,
On Fri, 8 Aug 2014 12:18:51 -0300, Ezequiel Garcia wrote:
> + ge0_pins: ge0_pins {
Would it make sense to name that ge0_rgmii_pins ? And ditto for ge1 ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-09 15:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 15:18 [PATCH 0/6] mvebu: Network devicetree pin muxing Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 1/6] ARM: mvebu: Add required ethernet muxing for the Armada 370 SoC Ezequiel Garcia
2014-08-09 15:19 ` Thomas Petazzoni [this message]
2014-08-09 16:31 ` Ezequiel Garcia
2014-08-10 12:16 ` Sebastian Hesselbarth
2014-08-11 11:38 ` Ezequiel Garcia
2014-08-10 12:21 ` Sebastian Hesselbarth
2014-08-08 15:18 ` [PATCH 2/6] ARM: mvebu: Add proper pin muxing on Globalscale Mirabox board Ezequiel Garcia
2014-08-08 17:12 ` Andrew Lunn
2014-08-08 18:21 ` Ezequiel Garcia
2014-08-08 19:21 ` Andrew Lunn
2014-08-08 19:47 ` Ezequiel Garcia
2014-08-09 15:21 ` Thomas Petazzoni
2014-08-09 15:52 ` Ezequiel Garcia
2014-08-09 15:57 ` Jason Cooper
2014-08-10 17:38 ` Thomas Petazzoni
2014-08-10 21:23 ` Andrew Lunn
2014-08-08 15:18 ` [PATCH 3/6] ARM: mvebu: Add proper pin muxing on the Armada 370 DB board Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 4/6] ARM: mvebu: Add proper pin muxing on Netgear ReadyNAS 102 Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 5/6] ARM: mvebu: Add proper pin muxing on Netgear ReadyNAS 104 Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 6/6] ARM: mvebu: Add proper pin muxing on Armada 370 RD board Ezequiel Garcia
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=20140809171902.7b5d45cc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.