From: Guenter Roeck <linux@roeck-us•net>
To: Neelesh Gupta <neelegup@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org, jdelvare@suse•de,
lm-sensors@lm-sensors•org
Cc: sbhat@linux•vnet.ibm.com
Subject: Re: [PATCH v2] powerpc/powernv: hwmon driver for power values, fan rpm and temperature
Date: Mon, 26 May 2014 07:12:03 -0700 [thread overview]
Message-ID: <53834BB3.10303@roeck-us.net> (raw)
In-Reply-To: <5382DD9B.2020406@linux.vnet.ibm.com>
On 05/25/2014 11:22 PM, Neelesh Gupta wrote:
> Any updates on the patch.
>
Not yet, I have been too busy with other stuff. That happens, unfortunately.
Guenter
next prev parent reply other threads:[~2014-05-26 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 14:26 [PATCH v2] powerpc/powernv: hwmon driver for power values, fan rpm and temperature Neelesh Gupta
2014-05-26 6:22 ` Neelesh Gupta
2014-05-26 14:12 ` Guenter Roeck [this message]
2014-05-28 7:23 ` Guenter Roeck
2014-05-28 7:41 ` Benjamin Herrenschmidt
2014-05-30 14:05 ` Neelesh Gupta
2014-06-09 8:15 ` Neelesh Gupta
2014-06-18 8:43 ` Neelesh Gupta
2014-06-18 13:05 ` Guenter Roeck
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=53834BB3.10303@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=jdelvare@suse$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lm-sensors@lm-sensors$(echo .)org \
--cc=neelegup@linux$(echo .)vnet.ibm.com \
--cc=sbhat@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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