public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: linux-kernel@vger.kernel.org, davej@suse.com
Cc: Philip.Blundell@pobox.com, tim@cyberelk.net
Subject: [PATCH] -- Needed since at least 2.5.2-pre8  -- Compile error in parport_cs.c: 327: `LP_MAJOR' undeclared
Date: Thu, 28 Feb 2002 20:40:58 -0800	[thread overview]
Message-ID: <3C7F065A.5060908@megapathdsl.net> (raw)

As you can see, this problem has been known for a while:

 > Subject:  2.5.2-pre8 -- Compile error in parport_cs.c: 327: `LP_MAJOR'
 > From:     Miles Lane <miles@megapathdsl.net>
 > Date:     2002-01-05 8:29:55

parport_cs.c: In function `parport_config':
parport_cs.c:327: `LP_MAJOR' undeclared (first use in this function)
make[2]: *** [parport_cs.o] Error 1
make[2]: Leaving directory `/usr/src/linux/drivers/parport'

This patch is from Evgeniy Polyakov <johnpol@2ka.mipt.ru>.
Please apply, unless the parallel port maintainers spot a problem.

--- ./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.
+ */

  /*====================================================================*/



                 reply	other threads:[~2002-03-01  4:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C7F065A.5060908@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=Philip.Blundell@pobox.com \
    --cc=davej@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@cyberelk.net \
    /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