From mboxrd@z Thu Jan  1 00:00:00 1970
From: linux@roeck-us.net (Guenter Roeck)
Date: Mon, 24 Sep 2012 10:18:17 -0700
Subject: [PATCH v4] hwmon: Versatile Express hwmon driver
In-Reply-To: <1348502972.27071.16.camel@hornet>
References: <1348246591-2409-1-git-send-email-mail@pawelmoll.com>
 <20120924155947.GA14060@roeck-us.net>
 <1348502972.27071.16.camel@hornet>
Message-ID: <20120924171817.GA29274@roeck-us.net>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On Mon, Sep 24, 2012 at 05:09:32PM +0100, Pawel Moll wrote:
> On Mon, 2012-09-24 at 16:59 +0100, Guenter Roeck wrote:
> > On Fri, Sep 21, 2012 at 05:56:31PM +0100, Pawel Moll wrote:
> > > From: Pawel Moll <pawel.moll@arm.com>
> > > 
> > > hwmon framework driver for Versatile Express sensors, providing
> > > information about board level voltage (only when regulator driver
> > > is not configured), currents, temperature and power/energy usage.
> > > Labels for the values can be defined as DT properties.
> > > 
> > > Signed-off-by: Pawel Moll <pawel.moll@arm.com>
> > 
> > After my concern was clarified ...
> > 
> > Acked-by: Guenter Roeck <linux@roeck-us.net>
> 
> Thanks a lot!
> 
> > I assume this will go upstream through the arm tree ?
> 
> I was planning to push the subsystem patches (hwmon, regulator etc.)
> through respective maintainers, so through your tree - the driver
> depends on VEXPRESS_CONFIG so won't cause any build issues before the
> infrastructure is in place. Of course if you'd rather see it go through
> arm-soc, I'll add it to that branch. Just let me know what is your
> preference.
> 
Since the driver can not be built w/o the rest of the infrastructure,
I think it should be pushed through a tree where it can. This way we also
make sure that it is in sync with its infrastructure, and avoid bad surprises
late in the game.

Thanks,
Guenter