From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "Semwal, Sumit" <sumit.semwal@ti.com>,
"Guruswamy, Senthilvadivu" <svadivu@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [omap-for-linus] Un-used DSS regulator data
Date: Mon, 28 Feb 2011 10:59:52 +0200 [thread overview]
Message-ID: <1298883592.9809.1.camel@deskari> (raw)
In-Reply-To: <a46904cc06b5f68124e65086b9961d02@mail.gmail.com>
Hi,
On Mon, 2011-02-28 at 02:50 -0600, Shilimkar, Santosh wrote:
> Tomi/Sumit,
>
> Today while building Tony's 'omap-for-linus' branch I came
> across below build warning.
> warning: 'sdp3430_vdda_dac_supply' defined but not used
>
> It seems the DSS regulator data is not being used. Are you missing
> any patch which will use it eventually?
It was an accidental left over from conflict resolving. I have a patch
in DSS tree which removes the regulator supply.
Tomi
next prev parent reply other threads:[~2011-02-28 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 8:50 [omap-for-linus] Un-used DSS regulator data Santosh Shilimkar
2011-02-28 8:59 ` Tomi Valkeinen [this message]
2011-02-28 9:03 ` Santosh Shilimkar
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=1298883592.9809.1.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=sumit.semwal@ti.com \
--cc=svadivu@ti.com \
--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