All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [lm-sensors] [PATCH v4] hwmon: Versatile Express hwmon driver
Date: Mon, 24 Sep 2012 17:18:17 +0000	[thread overview]
Message-ID: <20120924171817.GA29274@roeck-us.net> (raw)
In-Reply-To: <1348502972.27071.16.camel@hornet>

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

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] hwmon: Versatile Express hwmon driver
Date: Mon, 24 Sep 2012 10:18:17 -0700	[thread overview]
Message-ID: <20120924171817.GA29274@roeck-us.net> (raw)
In-Reply-To: <1348502972.27071.16.camel@hornet>

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

  reply	other threads:[~2012-09-24 17:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 16:56 [lm-sensors] [PATCH v4] hwmon: Versatile Express hwmon driver Pawel Moll
2012-09-21 16:56 ` Pawel Moll
2012-09-21 18:18 ` [lm-sensors] " Guenter Roeck
2012-09-21 18:18   ` Guenter Roeck
2012-09-24 12:03   ` [lm-sensors] " Pawel Moll
2012-09-24 12:03     ` Pawel Moll
2012-09-24 12:08     ` [lm-sensors] " Jean Delvare
2012-09-24 12:08       ` Jean Delvare
2012-09-24 12:28       ` [lm-sensors] " Guenter Roeck
2012-09-24 12:28         ` Guenter Roeck
2012-09-24 15:59 ` [lm-sensors] " Guenter Roeck
2012-09-24 15:59   ` Guenter Roeck
2012-09-24 16:09   ` [lm-sensors] " Pawel Moll
2012-09-24 16:09     ` Pawel Moll
2012-09-24 17:18     ` Guenter Roeck [this message]
2012-09-24 17:18       ` Guenter Roeck
2012-09-24 17:24       ` [lm-sensors] " Pawel Moll
2012-09-24 17:24         ` Pawel Moll

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=20120924171817.GA29274@roeck-us.net \
    --to=linux@roeck-us.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.