From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anuj Aggarwal <anuj.aggarwal@ti.com>
Cc: linux-omap@vger.kernel.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH 1/6] Regulator: Creating TWL4030 specific file having supplies & init data
Date: Mon, 11 Jan 2010 11:18:29 +0000 [thread overview]
Message-ID: <20100111111829.GD20717@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1262973463-32492-1-git-send-email-anuj.aggarwal@ti.com>
On Fri, Jan 08, 2010 at 11:27:43PM +0530, Anuj Aggarwal wrote:
> A new file for TWL4030/TPS65950 is created which has common supplies
> and regulator init data structures. They will be referenced from the
> various board-evm files depending upon the EVM requirements.
>
> Signed-off-by: Anuj Aggarwal <anuj.aggarwal@ti.com>
> ---
> arch/arm/mach-omap2/board-omap35x-twl4030-pmic.c | 175 ++++++++++++++++++++++
> 1 files changed, 175 insertions(+), 0 deletions(-)
Shouldn't there be a header file as well?
next prev parent reply other threads:[~2010-01-11 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 17:57 [PATCH 1/6] Regulator: Creating TWL4030 specific file having supplies & init data Anuj Aggarwal
2010-01-11 11:18 ` Mark Brown [this message]
2010-01-11 11:35 ` Mike Rapoport
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=20100111111829.GD20717@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anuj.aggarwal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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