All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Heilbrun <heilb@megapathdsl.com>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.21 pnpbios compile error.
Date: Sun, 9 Jun 2002 23:33:27 -0700	[thread overview]
Message-ID: <20020610063327.GA19217@paypal.com> (raw)
In-Reply-To: <200206101347.07394.corporal_pisang@counter-strike.com.my>

On Mon, Jun 10, 2002 at 01:47:07PM +0800, Corporal Pisang wrote:
> I get this error compiling 2.5.21
> 
> make[2]: Entering directory `/usr/src/linux/drivers/pnp'
>   gcc -Wp,-MD,.pnpbios_proc.o.d -D__KERNEL__ -I/usr/src/linux/include -Wall 
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer 
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 
> -march=athlon  -nostdinc -iwithprefix include    
> -DKBUILD_BASENAME=pnpbios_proc   -c -o pnpbios_proc.o pnpbios_proc.c
> pnpbios_proc.c:193: parse error before "pnpbios_proc_init"

Another casualty of the recent header cleanup. Trivial patch
below. The rest of the files in this directory look clean as far as
__init and __exit calls go.

diff -Nur linux-2.5/drivers/pnp/pnpbios_proc.c~ linux-2.5/drivers/pnp/pnpbios_proc.c
--- linux-2.5/drivers/pnp/pnpbios_proc.c~	Sun Jun  9 23:01:13 2002
+++ linux-2.5/drivers/pnp/pnpbios_proc.c	Sun Jun  9 23:01:24 2002
@@ -28,6 +28,7 @@
 #include <linux/types.h>
 #include <linux/proc_fs.h>
 #include <linux/pnpbios.h>
+#include <linux/init.h>
 
 static struct proc_dir_entry *proc_pnp = NULL;
 static struct proc_dir_entry *proc_pnp_boot = NULL;


-- 

Thank you,

Brad Heilbrun
Administrator, Network Operations
PayPal, Inc.
650.864.8200 - noc@paypal.com


      reply	other threads:[~2002-06-10  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10  5:47 2.5.21 pnpbios compile error Corporal Pisang
2002-06-10  6:33 ` Brad Heilbrun [this message]

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=20020610063327.GA19217@paypal.com \
    --to=heilb@megapathdsl.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 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.