From: Stephen Warren <swarren@wwwdotorg.org>
To: Stefan Wahren <stefan.wahren@i2se.com>, lee@kernel.org
Cc: linux@arm.linux.org.uk, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] ARM: bcm2835: Use pinctrl header
Date: Sat, 17 Jan 2015 20:06:34 -0700 [thread overview]
Message-ID: <54BB233A.10902@wwwdotorg.org> (raw)
In-Reply-To: <1421426993-27264-1-git-send-email-stefan.wahren@i2se.com>
On 01/16/2015 09:49 AM, Stefan Wahren wrote:
> This patch converts all bcm2835 dts files to use the pinctrl
> header file.
Aside from the one comment I made, the series,
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
prev parent reply other threads:[~2015-01-18 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:49 [PATCH 4/4] ARM: bcm2835: Use pinctrl header Stefan Wahren
2015-01-18 3:06 ` Stephen Warren [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=54BB233A.10902@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.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