public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Date: Mon, 06 May 2013 15:31:25 -0600	[thread overview]
Message-ID: <5188212D.3030904@wwwdotorg.org> (raw)
In-Reply-To: <1367874058-2378-2-git-send-email-eduardo.valentin@ti.com>

On 05/06/2013 03:00 PM, Eduardo Valentin wrote:
> Introduce HAS_BANDGAP config entry. This config is a
> boolean value so that arch code can flag is they
> feature a bandgap device.

What does this patch have to do with device tree (there's "dts" in the
subject)? What's a BANDGAP device?

  reply	other threads:[~2013-05-06 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1367874058-2378-1-git-send-email-eduardo.valentin@ti.com>
2013-05-06 21:00 ` [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP Eduardo Valentin
2013-05-06 21:31   ` Stephen Warren [this message]
2013-05-07  0:20     ` Eduardo Valentin
2013-05-06 21:34   ` Aaro Koskinen
2013-05-06 22:36     ` Jason Gunthorpe
2013-05-07  0:23       ` Eduardo Valentin
2013-05-07  0:36         ` Jason Gunthorpe
2013-05-07 13:15           ` Eduardo Valentin
2013-05-07 18:27             ` Jason Gunthorpe
2013-05-07 19:06               ` Aaro Koskinen
2013-05-08  6:04                 ` Tomi Valkeinen
2013-05-06 22:40     ` Eduardo Valentin
2013-05-06 21:00 ` [RESEND][PATCH 2/3] arm: dts: add bandgap entry for OMAP443x devices Eduardo Valentin
2013-05-06 21:00 ` [RESEND][PATCH 3/3] arm: add bandgap entry for OMAP4460 devices Eduardo Valentin

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=5188212D.3030904@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=eduardo.valentin@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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