From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Problems while designing TPS65023 regulator driver
Date: Fri, 3 Apr 2009 17:05:31 -0700 [thread overview]
Message-ID: <20090404000531.GE8840@atomide.com> (raw)
In-Reply-To: <20090403085335.GA3759@sirena.org.uk>
* Mark Brown <broonie@sirena.org.uk> [090403 01:53]:
> On Fri, Apr 03, 2009 at 01:33:58PM +0530, Aggarwal, Anuj wrote:
>
> > I could not find the commit in linux-OMAP git where the init data is
> > passed as a parameter to the regulator_register(). I am dependent
> > on this commit for my TPS65023 regulator driver and could not push
> > my patch without the commit being in l-o.
>
> > Any idea when this would be available in l-o?
>
> I can't speak for the OMAP tree but the patch should appear in
> 2.6.30-rc1 so presumably it'll get merged into OMAP some time after that
> is released.
Sounds good to me.
Tony
next prev parent reply other threads:[~2009-04-04 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 9:11 Problems while designing TPS65023 regulator driver Aggarwal, Anuj
2009-02-26 14:04 ` Mark Brown
2009-03-05 12:03 ` Aggarwal, Anuj
2009-03-06 13:34 ` Mark Brown
2009-03-07 0:07 ` David Brownell
2009-03-07 16:22 ` Mark Brown
2009-03-08 20:54 ` David Brownell
2009-03-08 22:41 ` Mark Brown
2009-03-10 0:45 ` David Brownell
2009-03-10 23:33 ` Mark Brown
2009-04-03 8:03 ` Aggarwal, Anuj
2009-04-03 8:53 ` Mark Brown
2009-04-04 0:05 ` Tony Lindgren [this message]
2009-04-23 13:30 ` Trilok Soni
2009-04-23 22:17 ` David Brownell
2009-04-24 6:01 ` Trilok Soni
2009-04-24 6:05 ` Aggarwal, Anuj
2009-04-24 6:32 ` David Brownell
2009-04-24 8:12 ` Aggarwal, Anuj
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=20090404000531.GE8840@atomide.com \
--to=tony@atomide.com \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.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