From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, balbir@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com,
davej@codemonkey.org.uk,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: [BUG] While changing the cpufreq governor, kernel hits a bug in workqueue.c
Date: Tue, 07 Oct 2008 15:11:51 +0530 [thread overview]
Message-ID: <48EB2EDF.5000605@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y73129ik.fsf@skyscraper.fehenstaub.lan>
Any updates on this bug. Thanks in advance for your coordination.
Johannes Weiner wrote:
>> I have not yet looked at cpufreq_conservative...
>>
>> Thanks for your patience and insistence,
>>
>> Hannes
Thanks and Regards
R.Nageswara Sastry
next prev parent reply other threads:[~2008-10-07 9:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 10:51 [BUG] While changing the cpufreq governor, kernel hits a bug in workqueue.c Nageswara R Sastry
2008-06-23 15:26 ` Johannes Weiner
2008-06-24 9:17 ` Nageswara R Sastry
2008-06-25 19:47 ` Johannes Weiner
2008-06-25 20:00 ` Dave Jones
2008-06-26 12:18 ` Nageswara R Sastry
2008-06-26 13:31 ` Nageswara R Sastry
2008-06-27 4:12 ` Nageswara R Sastry
2008-07-01 14:00 ` Johannes Weiner
2008-07-04 13:56 ` Johannes Weiner
2008-07-07 9:48 ` Nageswara R Sastry
2008-07-07 11:07 ` Johannes Weiner
2008-07-08 5:52 ` Nageswara R Sastry
2008-07-10 11:11 ` Johannes Weiner
2008-07-15 3:42 ` Nageswara R Sastry
2008-07-16 13:44 ` Peter Zijlstra
2008-08-12 8:12 ` Nageswara R Sastry
2008-08-12 21:29 ` Johannes Weiner
2008-08-12 21:44 ` Johannes Weiner
2008-10-07 9:41 ` Nageswara R Sastry [this message]
2008-10-28 3:29 ` Nageswara R Sastry
2008-07-07 11:19 ` Nageswara R Sastry
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=48EB2EDF.5000605@linux.vnet.ibm.com \
--to=rnsastry@linux.vnet.ibm.com \
--cc=astarikovskiy@suse.de \
--cc=balbir@linux.vnet.ibm.com \
--cc=davej@codemonkey.org.uk \
--cc=ego@linux.vnet.ibm.com \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=svaidy@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@intel.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