From: Dominik Brodowski <linux@dominikbrodowski.de>
To: davej@redhat.com, cpufreq@www.linux.org.uk
Subject: [PATCH] fix cpufreq_update_policy
Date: Wed, 28 Jan 2004 22:52:49 +0100 [thread overview]
Message-ID: <20040128215249.GA4727@dominikbrodowski.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
Fix a brown paper bug in drivers/cpufreq/cpufreq.c which accessed random
memory instead of the correct struct.
Please apply,
diff -ruN linux-original/drivers/cpufreq/cpufreq.c linux/drivers/cpufreq/cpufreq.c
--- linux-original/drivers/cpufreq/cpufreq.c 2004-01-16 20:30:59.000000000 +0100
+++ linux/drivers/cpufreq/cpufreq.c 2004-01-28 22:16:38.099398456 +0100
@@ -868,7 +868,7 @@
down(&data->lock);
memcpy(&policy,
- &data,
+ data,
sizeof(struct cpufreq_policy));
policy.min = data->user_policy.min;
policy.max = data->user_policy.max;
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next reply other threads:[~2004-01-28 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 21:52 Dominik Brodowski [this message]
2004-01-28 22:12 ` [PATCH] fix cpufreq_update_policy Dmitry Torokhov
2004-01-28 22:16 ` Dominik Brodowski
2004-01-29 0:24 ` Dmitry Torokhov
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=20040128215249.GA4727@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.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