public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Shawn P. Garbett" <listman-qZIqNUI/gJRAfugRpC6u6w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: 2.5.64 kernel bug
Date: Fri, 7 Mar 2003 11:49:33 -0600	[thread overview]
Message-ID: <200303071149.33553.listman@garbett.org> (raw)

I just got a P2120 laptop and really really want ACPI working. I grabbed the 
2.5.64 kernel and it didn't compile. Looking back through the archives of 
this list I found nothing related to this. 

I'm a proficient programmer, but have never done any serious kernel work under 
linux. 

Here's what I changed to make it compile: 

sputnik:/usr/src/linux# diff drivers/cpufreq/userspace.c.orig 
drivers/cpufreq/userspace.c
514c514
<               device_create_file (policy->intf.dev, 
&dev_attr_scaling_setspeed );
---
>               device_create_file (policy->dev, &dev_attr_scaling_setspeed);
523c523
<               device_remove_file (policy->intf.dev, 
&dev_attr_scaling_setspeed
);
---
>               device_remove_file (policy->dev, &dev_attr_scaling_setspeed);



Shawn


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

             reply	other threads:[~2003-03-07 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 17:49 Shawn P. Garbett [this message]
     [not found] ` <200303071149.33553.listman-qZIqNUI/gJRAfugRpC6u6w@public.gmane.org>
2003-03-07 17:34   ` 2.5.64 kernel bug Patrick Mochel
     [not found]     ` <Pine.LNX.4.33.0303071128380.991-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-03-08  3:42       ` Alexander Hoogerhuis

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=200303071149.33553.listman@garbett.org \
    --to=listman-qziqnui/gjrafugrpc6u6w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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