All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Miller <rem@osdl.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>, mochel@osdl.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bugme-new] [Bug 442] New: compile failure in drivers/cpufreq/userspace.c (fwd)
Date: Wed, 5 Mar 2003 16:22:25 -0800	[thread overview]
Message-ID: <20030306002225.GA10819@doc.pdx.osdl.net> (raw)
In-Reply-To: <657950000.1046904813@flay>

On Wed, Mar 05, 2003 at 02:53:33PM -0800, Martin J. Bligh wrote:
>   gcc -Wp,-MD,drivers/cpufreq/.userspace.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe
> -mpreferred-stack-boundary=2 -march=athlon -Iinclude/asm-i386/mach-default
> -nostdinc -iwithprefix include    -DKBUILD_BASENAME=userspace
> -DKBUILD_MODNAME=userspace -c -o drivers/cpufreq/.tmp_userspace.o
> drivers/cpufreq/userspace.c
> drivers/cpufreq/userspace.c: In function `cpufreq_governor_userspace':
> drivers/cpufreq/userspace.c:514: structure has no member named `intf'
> drivers/cpufreq/userspace.c:523: structure has no member named `intf'
> make[2]: *** [drivers/cpufreq/userspace.o] Error 1
> make[1]: *** [drivers/cpufreq] Error 2
> make: *** [drivers] Error 2

I believe the patch below fixes the problem.  Pat?

-- 
Bob Miller					Email: rem@osdl.org
Open Source Development Lab			Phone: 503.626.2455 Ext. 17


===== userspace.c 1.1 vs edited =====
--- 1.1/drivers/cpufreq/userspace.c	Sun Feb 16 05:23:39 2003
+++ edited/userspace.c	Wed Mar  5 16:12:16 2003
@@ -511,7 +511,7 @@
 		cpu_min_freq[cpu] = policy->min;
 		cpu_max_freq[cpu] = policy->max;
 		cpu_cur_freq[cpu] = policy->cur;
-		device_create_file (policy->intf.dev, &dev_attr_scaling_setspeed);
+		device_create_file (policy->dev, &dev_attr_scaling_setspeed);
 		memcpy (&current_policy[cpu], policy, sizeof(struct cpufreq_policy));
 		up(&userspace_sem);
 		break;
@@ -520,7 +520,7 @@
 		cpu_is_managed[cpu] = 0;
 		cpu_min_freq[cpu] = 0;
 		cpu_max_freq[cpu] = 0;
-		device_remove_file (policy->intf.dev, &dev_attr_scaling_setspeed);
+		device_remove_file (policy->dev, &dev_attr_scaling_setspeed);
 		up(&userspace_sem);
 		module_put(THIS_MODULE);
 		break;

  reply	other threads:[~2003-03-06  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 22:53 [Bugme-new] [Bug 442] New: compile failure in drivers/cpufreq/userspace.c (fwd) Martin J. Bligh
2003-03-06  0:22 ` Bob Miller [this message]
2003-03-06  0:00   ` Patrick Mochel

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=20030306002225.GA10819@doc.pdx.osdl.net \
    --to=rem@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mochel@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.