From: Rob Herring <robh@kernel.org>
To: tthayer@opensource.altera.com
Cc: lee.jones@linaro.org, mark.rutland@arm.com,
dinguyen@opensource.altera.com, inux@armlinux.org.uk,
arnd@arndb.de, gregkh@linuxfoundation.org, davem@davemloft.net,
geert@linux-m68k.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] dt-bindings: mfd: Add Altera Arria10 SR Monitor
Date: Tue, 18 Oct 2016 09:05:48 -0500 [thread overview]
Message-ID: <20161018140548.su5ffrjqrxlk4cyf@rob-hp-laptop> (raw)
In-Reply-To: <1476394329-31696-2-git-send-email-tthayer@opensource.altera.com>
On Thu, Oct 13, 2016 at 04:32:06PM -0500, tthayer@opensource.altera.com wrote:
> From: Thor Thayer <tthayer@opensource.altera.com>
>
> Add the Arria10 DevKit System Resource Chip register and state
> monitoring module to the MFD.
>
> Signed-off-by: Thor Thayer <tthayer@opensource.altera.com>
> ---
> Note: This needs to be applied to the bindings document that
> was Acked & Applied but didn't reach the for-next branch.
> See https://patchwork.ozlabs.org/patch/629397/
> ---
> ---
> .../devicetree/bindings/mfd/altera-a10sr.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-10-18 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 21:32 [PATCH 0/4] Add Altera A10SR Status & Control Monitor tthayer
2016-10-13 21:32 ` [PATCH 1/4] dt-bindings: mfd: Add Altera Arria10 SR Monitor tthayer
2016-10-18 14:05 ` Rob Herring [this message]
2016-10-26 12:51 ` Lee Jones
2016-10-13 21:32 ` [PATCH 2/4] misc: Add Altera Arria10 System Resource Control tthayer
2016-10-13 21:32 ` [PATCH 3/4] mfd: altr-a10sr: Add Arria10 SR Monitor tthayer
2016-10-26 12:52 ` Lee Jones
2016-10-26 15:18 ` Thor Thayer
2016-10-13 21:32 ` [PATCH 4/4] ARM: socfpga: dts: Add Monitor to A10-SR MFD tthayer
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=20161018140548.su5ffrjqrxlk4cyf@rob-hp-laptop \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=inux@armlinux.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tthayer@opensource.altera.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;
as well as URLs for NNTP newsgroup(s).