From: Romit Dasgupta <romit@ti.com>
To: "Menon, Nishanth" <nm@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/10] OPP layer and additional cleanups.
Date: Thu, 07 Jan 2010 18:25:10 +0530 [thread overview]
Message-ID: <4B45D9AE.1040502@ti.com> (raw)
In-Reply-To: <4B4266F3.5000501@ti.com>
Menon, Nishanth wrote:
> >
> > Could you please start using git format-patch -s -M -o to generate patches?
> >
> > And you exposed struct omap_opp back to the public defeating the
> > previous work :(
Exposing struct omap_opp is ok. In fact I need this for adding/deleting and
getting a handle on a particular OPP. My actual intent is to have the
book-keeping done only in OPP layer. Now you just need to search by saying
find_opp_by_freq(OPP_MPU, required_freq, flags /* flag will define the search
criteria */);
> >
> > mostly I like what you are trying to do here, but just not exactly what
> > you are doing :(
Please let me know how to improvise this.
prev parent reply other threads:[~2010-01-07 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 13:29 [PATCH 2/10] OPP layer and additional cleanups Romit Dasgupta
[not found] ` <4B4266F3.5000501@ti.com>
2010-01-07 12:55 ` Romit Dasgupta [this message]
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=4B45D9AE.1040502@ti.com \
--to=romit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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