From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] driver for the hardware monitoring chip in the Zyxel NSA320
Date: Tue, 08 Mar 2016 14:01:06 +0100 [thread overview]
Message-ID: <87mvq93yzx.fsf@free-electrons.com> (raw)
In-Reply-To: <20160308115506.GA25899@roeck-us.net> (Guenter Roeck's message of "Tue, 8 Mar 2016 03:55:06 -0800")
Hi Adam and Guenter,
On mar., mars 08 2016, Guenter Roeck <linux@roeck-us.net> wrote:
> On Sat, Mar 05, 2016 at 03:34:54PM +0000, Adam Baker wrote:
>> Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt | 21 +++++
>> Documentation/hwmon/nsa320 | 53 +++++++++++
>> arch/arm/boot/dts/kirkwood-nsa320.dts | 13 ++-
>> drivers/hwmon/Kconfig | 15 +++
>> drivers/hwmon/Makefile | 1 +
>> drivers/hwmon/nsa320-hwmon.c | 216 ++++++++++++++++++++++++++++++++++++++++++++
>> 6 files changed, 317 insertions(+), 2 deletions(-)
>>
> Patch 1/3 and 2/3 applied to hwmon-next.
>
> I assume that patch 3/3 will go through the arm tree.
Yes but now that the rc7 was released is too late putting it to arm-soc
for the 4.6 kernel.
Gregory
>
> Guenter
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2016-03-08 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 15:34 [PATCH v4 0/3] driver for the hardware monitoring chip in the Zyxel NSA320 Adam Baker
2016-03-05 15:34 ` [PATCH v4 1/3] hwmon: Define binding for the nsa320-hwmon driver Adam Baker
2016-03-05 15:34 ` [PATCH v4 2/3] hwmon: Create an NSA320 hardware monitoring driver Adam Baker
2016-03-05 15:34 ` [PATCH v4 3/3] ARM: mvebu: Add the hardware monitor to the NSA320 device tree Adam Baker
2016-03-29 15:45 ` Gregory CLEMENT
2016-03-08 11:55 ` [PATCH v4 0/3] driver for the hardware monitoring chip in the Zyxel NSA320 Guenter Roeck
2016-03-08 13:01 ` Gregory CLEMENT [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=87mvq93yzx.fsf@free-electrons.com \
--to=gregory.clement@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 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).