All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: Alexander Clouter <alex@digriz.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, jun.nakajima@intel.com,
	davej@redhat.com
Subject: Re: OOPS: 2.6.16-rc6 cpufreq_conservative
Date: Sun, 19 Mar 2006 09:06:25 -0500	[thread overview]
Message-ID: <200603190906.25174.kernel-stuff@comcast.net> (raw)
In-Reply-To: <20060319120047.GA26018@inskipp.digriz.org.uk>

On Sunday 19 March 2006 07:00, Alexander Clouter wrote:
> Well its drifted a bit, however I submitted a number of patches here about
> two weeks ago to bring it back into line and hopefully make it HOTPLUG
> safe.
>
> The new set of patches pretty much make conservative's codebase identical
> to ondemands....as no one has posted back having used these or anything
> what am I to do?!

The codebase already seems identical to ondemand - Are your patches in 
2.6.16-rc6 or -mm? If they are - let me know which. If you posted them but 
they haven't yet made it into either -mm or mainline can you please post 
links to all your patches please? I can test them.

Why do we even have conservative and ondemand as two separate modules given 
they share huge amount of code - perhaps make conservative an optional 
behaviour of ondemand or alteast make a common lib which both use?

Thanks
Parag

  reply	other threads:[~2006-03-19 14:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 20:25 OOPS: 2.6.16-rc6 cpufreq_conservative Parag Warudkar
2006-03-18 21:40 ` Linus Torvalds
2006-03-18 22:09   ` Parag Warudkar
2006-03-18 23:12     ` Linus Torvalds
2006-03-18 22:26   ` Parag Warudkar
2006-03-19  0:53   ` Andrew Morton
2006-03-19  2:38     ` Linus Torvalds
2006-03-19  5:08       ` Paul Jackson
2006-03-19 17:43         ` Linus Torvalds
2006-03-19 18:46       ` Linus Torvalds
2006-03-19 19:02         ` Linus Torvalds
2006-03-19 19:33           ` Linus Torvalds
2006-03-19 19:40             ` Al Viro
2006-03-19 20:01               ` Linus Torvalds
2006-03-19 20:31                 ` Linus Torvalds
2006-03-19 20:47                   ` Andrew Morton
2006-03-19 22:18                     ` Linus Torvalds
2006-03-19 22:35                       ` Andrew Morton
2006-03-19 22:55                         ` Linus Torvalds
2006-03-19 22:46                       ` Linus Torvalds
2006-03-19 23:04                         ` Andrew Morton
2006-03-19 20:57                   ` Parag Warudkar
2006-03-20  6:12             ` Willy Tarreau
2006-03-20  6:26               ` Linus Torvalds
2006-03-20  7:18                 ` Willy Tarreau
2006-03-21  6:32                   ` Willy Tarreau
2006-03-20  8:22               ` Peter T. Breuer
2006-03-19  6:34     ` Parag Warudkar
2006-03-19 12:00       ` Alexander Clouter
2006-03-19 14:06         ` Parag Warudkar [this message]
2006-03-19 17:34           ` Alexander Clouter

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=200603190906.25174.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=akpm@osdl.org \
    --cc=alex@digriz.org.uk \
    --cc=davej@redhat.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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.