From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: linux-sh@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: porter: add SDHI0/2 DT support
Date: Wed, 7 Oct 2015 22:34:48 +0300 [thread overview]
Message-ID: <561573D8.6060203@cogentembedded.com> (raw)
In-Reply-To: <20151007033957.GA30650@verge.net.au>
On 10/07/2015 06:39 AM, Simon Horman wrote:
>> Define the Porter board dependent part of the SDHI0/2 device nodes along with
>> the necessary voltage regulators (note that the Vcc regulators are dummy --
>> they are required but don't actually exist on the board). Also, GPIOs have to
>> be used for the CD and WP signals due to the SDHI driver constraints...
>>
>> This patch is analogous to the commit 1299df03d719 (ARM: shmobile: henninger:
>> add SDHI0/2 DT support) as there are no differences between those boards in
>> this respect.
>>
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>
>> ---
>> This patch is against the 'renesas-devel-20151006-v4.3-rc4' tag of Simon
>> Horman's 'renesas.git' repo.
>
> Thanks I have queued this up after addressing some issues
> in the changelog that checkpatch complained about:
> * text > 75 characters wide
> * Missing '"' around name of patch referred to
Sorry about that, forgot to run thru checkpatch.pl (as usual :-).
MBR, Sergei
next prev parent reply other threads:[~2015-10-07 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 23:05 [PATCH] ARM: shmobile: porter: add SDHI0/2 DT support Sergei Shtylyov
2015-10-07 3:39 ` Simon Horman
2015-10-07 11:02 ` Sergei Shtylyov
2015-10-08 2:12 ` Simon Horman
2015-10-08 10:54 ` Sergei Shtylyov
2015-10-08 11:08 ` Simon Horman
2015-10-07 19:34 ` Sergei Shtylyov [this message]
2015-10-08 2:13 ` 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=561573D8.6060203@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@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).