From: eduardo.valentin@ti.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Date: Mon, 6 May 2013 20:20:16 -0400 [thread overview]
Message-ID: <518848C0.2020808@ti.com> (raw)
In-Reply-To: <5188212D.3030904@wwwdotorg.org>
On 06-05-2013 17:31, Stephen Warren wrote:
> 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?
>
>
In fact, this one has nothing to do with DT. dts in the title is a typo..
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 295 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130506/00c6dace/attachment.sig>
next prev parent reply other threads:[~2013-05-07 0:20 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
2013-05-07 0:20 ` Eduardo Valentin [this message]
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=518848C0.2020808@ti.com \
--to=eduardo.valentin@ti.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).