All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Gross <mgross@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux-pm <linux-pm@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] QoS params patch
Date: Thu, 27 Sep 2007 08:37:33 -0700	[thread overview]
Message-ID: <20070927153733.GF25718@linux.intel.com> (raw)
In-Reply-To: <20070926210515.6725e745.randy.dunlap@oracle.com>

On Wed, Sep 26, 2007 at 09:05:15PM -0700, Randy Dunlap wrote:
> On Thu, 27 Sep 2007 11:24:40 +0900 Paul Mundt wrote:
> 
> > > +/* static helper functions */
> > > +static s32 max_compare(s32 v1, s32 v2)
> > > +{
> > > +	if (v1 < v2)
> > > +		return v2;
> > > +	else
> > > +		return v1;
> > > +}
> > > +
> > > +static s32 min_compare(s32 v1, s32 v2)
> > > +{
> > > +	if (v1 < v2)
> > > +		return v1;
> > > +	else
> > > +		return v2;
> > > +}
> > > +
> > min()/max() instead?
> 
> Other code wants function pointers to the min & max functions.
> That's why they are here AFAICT.
> 
> 
> > > +/* assumes qos_lock is held */
> > > +static void update_target(int i)
> > > +{
> > 'target' might be a more meaningful variable name.
> 
> Anything but 'i'.

The 'i' is gone.  Will post new patch later today.

--mgross

  reply	other threads:[~2007-09-27 15:38 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 22:37 [RFC] QoS power Management enabling patch set Mark Gross
2007-09-26 22:40 ` [RFC] QoS params patch Mark Gross
2007-09-26 23:41   ` Randy Dunlap
2007-09-26 23:41   ` Randy Dunlap
2007-09-27  0:40     ` Mark Gross
2007-09-27  0:40     ` Mark Gross
2007-09-27  2:53       ` Valdis.Kletnieks
2007-09-27  3:18         ` Paul Mundt
2007-09-27  3:18         ` Paul Mundt
2007-09-27 15:17           ` Mark Gross
2007-09-27 15:17           ` Mark Gross
2007-09-27 15:36         ` Mark Gross
2007-09-27 15:36         ` Mark Gross
2007-09-27  2:53       ` Valdis.Kletnieks
2007-09-27 13:00       ` roel
2007-09-27 13:00       ` roel
2007-09-27  2:24   ` Paul Mundt
2007-09-27  2:24   ` Paul Mundt
2007-09-27  4:05     ` Randy Dunlap
2007-09-27  4:05     ` Randy Dunlap
2007-09-27 15:37       ` Mark Gross [this message]
2007-09-27 15:37       ` Mark Gross
2007-09-27 20:17       ` [RFC] QoS params patch update Mark Gross
2007-09-28  0:08         ` Paul Mundt
2007-09-28  0:08         ` Paul Mundt
2007-09-27 20:17       ` Mark Gross
2007-09-27 16:21     ` [RFC] QoS params patch Mark Gross
2007-09-27 16:21     ` Mark Gross
2007-09-28  6:25   ` Andrew Morton
2007-09-28  6:41     ` Paul Mundt
2007-09-28 17:22       ` Mark Gross
2007-09-28 17:22       ` Mark Gross
2007-09-28  6:41     ` Paul Mundt
2007-09-28 17:19     ` Mark Gross
2007-09-28 18:51       ` Andrew Morton
2007-09-28 18:51       ` Andrew Morton
2007-10-01 16:11         ` Mark Gross
2007-10-01 16:11         ` Mark Gross
2007-09-28 17:19     ` Mark Gross
2007-09-28  6:25   ` Andrew Morton
2007-09-26 22:40 ` Mark Gross
2007-09-26 22:42 ` [RFC] QoS power Management enabling patch set Mark Gross
2007-09-26 22:42 ` Mark Gross
2007-09-26 22:45 ` [RFC] QoS power example / hack Mark Gross
2007-09-26 22:45 ` Mark Gross

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=20070927153733.GF25718@linux.intel.com \
    --to=mgross@linux.intel.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.