From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Chris Paterson <chris.paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH repost 0/2] ARM: shmobile: document iWave's iW-RainboW-G22D-SODIMM RZ/G1E SODIMM development platform
Date: Wed, 9 Aug 2017 12:27:38 +0100 [thread overview]
Message-ID: <cover.1502274234.git.fabrizio.castro@bp.renesas.com> (raw)
Hello,
This series aims to add the documentation for the device tree bindings
of the iWave iW-RainboW-G22D-SODIMM RZ/G1E SODIMM development kit:
http://www.iwavesystems.com/product/development-platform/sodimm-evaluation-boards/rz-g1e-sodimm-development-kit-28/rz-g1e-sodimm-development-kit.html
which consists of a System on Module (iW-RainboW-G22M-SM) and a carrier
card (iW-RainboW-G22D).
Regards,
Fabrizio Castro (2):
ARM: shmobile: document iW-RainboW-G22M-SM SODIMM System on Module
ARM: shmobile: document iW-RainboW-G22D SODIMM SOM Development
Platform
Documentation/devicetree/bindings/arm/shmobile.txt | 4 ++++
1 file changed, 4 insertions(+)
--
1.9.1
next reply other threads:[~2017-08-09 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 11:27 Fabrizio Castro [this message]
2017-08-09 11:27 ` [PATCH repost 1/2] ARM: shmobile: document iW-RainboW-G22M-SM SODIMM System on Module Fabrizio Castro
[not found] ` <cover.1502274234.git.fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-08-09 11:27 ` [PATCH repost 2/2] ARM: shmobile: document iW-RainboW-G22D SODIMM SOM Development Platform Fabrizio Castro
2017-08-10 8:11 ` [PATCH repost 0/2] ARM: shmobile: document iWave's iW-RainboW-G22D-SODIMM RZ/G1E SODIMM development platform Simon Horman
2017-08-17 8:30 ` Simon Horman
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=cover.1502274234.git.fabrizio.castro@bp.renesas.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).