From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Sean Young <sean@mess.org>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] AMD Elan SC520 cpufreq driver
Date: Wed, 30 Mar 2005 00:04:32 +0200 [thread overview]
Message-ID: <20050329220432.GA4018@isilmar.linta.de> (raw)
In-Reply-To: <20050329213658.GA12868@levin.pad.mess.org>
Hi,
> +#include <linux/slab.h>
What do you need slab.h for?
> + printk(KERN_INFO "sc520_freq: attempting to set frequency to %i kHz\n",
> + sc520_freq_table[state].frequency);
Please change this to a dprintk and use the cpufreq_debug infrastructure for
that -- users who want to use dynamic frequency scaling don't want to have
their dmesg flooded with printk's :)
> + policy->cpuinfo.transition_latency = CPUFREQ_ETERNAL;
Do you know how long a transition takes and for how long no other transition
may be done?
> + cpufreq_frequency_table_get_attr(sc520_freq_table, policy->cpu);
broken indenting
> + /* Test if we have the right hardware */
> + if (c->x86_vendor != X86_VENDOR_AMD ||
> + c->x86 != 4 || c->x86_model != 9) {
> + printk(KERN_INFO "sc520_freq: error: no Elan SC520 processor found!\n");
please do only a dprintk here as well, and I think a tab is missing, too.
Nice work :)
Thanks,
Dominik
next prev parent reply other threads:[~2005-03-29 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 21:36 [PATCH] AMD Elan SC520 cpufreq driver Sean Young
2005-03-29 21:50 ` Eric Piel
2005-03-29 23:42 ` Sean Young
2005-03-29 22:04 ` Dominik Brodowski [this message]
2005-04-03 16:27 ` Sean Young
2005-04-03 23:53 ` Eric Piel
2005-04-09 20:20 ` [PATCH] cpufreq: fix latency comment in cpufreq.h [Was: Re: [PATCH] AMD Elan SC520 cpufreq driver] Dominik Brodowski
2005-04-09 21:43 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2005-05-29 1:43 [PATCH] AMD Elan SC520 cpufreq driver Sean Young
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=20050329220432.GA4018@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=cpufreq@lists.linux.org.uk \
--cc=sean@mess.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