From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>, Dave Jones <davej@suse.de>
Cc: johnpol@2ka.mipt.ru
Subject: [PATCH] Re: 2.5.2-pre3 -- parport_cs.c:327: In function `parport_config': `LP_MAJOR' undeclared (first use in this function)
Date: 10 Feb 2002 19:18:53 -0800 [thread overview]
Message-ID: <1013397534.29598.32.camel@turbulence.megapathdsl.net> (raw)
In-Reply-To: <20020123105043.18eb56fd.johnpol@2ka.mipt.ru>
In-Reply-To: <1011771555.28121.0.camel@stomata.megapathdsl.net> <20020123105043.18eb56fd.johnpol@2ka.mipt.ru>
David,
This problem is still there is 2.5.4-pre6.
Can you accept this patch into your tree
and, if it looks right to you, attempt to
get the patch accepted into the "trivial and
obviously correct tiny patches" tree, if there
is one, yet? Patch is by Evgeniy Polyakov.
Miles
On Tue, 2002-01-22 at 23:50, Evgeniy Polyakov wrote:
> On 22 Jan 2002 23:39:12 -0800
> Miles Lane <miles@megapathdsl.net> wrote:
>
> > gcc -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 -DMODULE -c -o
> > parport_cs.o parport_cs.c parport_cs.c: In function `parport_config':
> > parport_cs.c:327: `LP_MAJOR' undeclared (first use in this function)
> > parport_cs.c:327: (Each undeclared identifier is reported only once
> > parport_cs.c:327: for each function it appears in.)
> > parport_cs.c: At top level:
> > parport_cs.c:109: warning: `parport_cs_ops' defined but not used
> > make[2]: *** [parport_cs.o] Error 1
> > make[2]: Leaving directory `/usr/src/linux/drivers/parport'
>
> Try this patch, but it is given WITHOUT ANY WARRANTY.
> I even cann't test to compile it.
> And there is not ieee card here.
> So, it was wrote with luck and common sense.
> I hope it will help you.
>
--- ./drivers/parport/parport_cs.c~ Sun Sep 30 23:26:08 2001
+++ ./drivers/parport/parport_cs.c Wed Jan 23 10:49:30 2002
@@ -45,6 +45,7 @@
#include <linux/string.h>
#include <linux/timer.h>
#include <linux/ioport.h>
+#include <linux/major.h>
#include <linux/parport.h>
#include <linux/parport_pc.h>
@@ -106,7 +107,9 @@
static dev_link_t *dev_list = NULL;
extern struct parport_operations parport_pc_ops;
-static struct parport_operations parport_cs_ops;
+/*static struct parport_operations parport_cs_ops;
+ * To make compiler happy.
+ */
/*====================================================================*/
prev parent reply other threads:[~2002-02-11 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 7:39 2.5.2-pre3 -- parport_cs.c:327: In function `parport_config': `LP_MAJOR' undeclared (first use in this function) Miles Lane
2002-01-23 7:50 ` Evgeniy Polyakov
2002-02-11 3:18 ` Miles Lane [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=1013397534.29598.32.camel@turbulence.megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=davej@suse.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).