From: Steve Martin <ecprod@bellsouth.net>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: IEEE1284 parport code won't build in 2.4.12
Date: Fri, 12 Oct 2001 08:56:58 -0400 [thread overview]
Message-ID: <3BC6E89A.BA8F98B6@bellsouth.net> (raw)
This has already been passed on to Tim Waugh, but here's
a heads-up:
drivers/parport/ieee1284_ops.c -- invokes an undefined
enum entry from parport.h -- as a result the code
won't build.
next reply other threads:[~2001-10-12 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 12:56 Steve Martin [this message]
2001-10-12 13:11 ` PROBLEM: IEEE1284 parport code won't build in 2.4.12 Jesper Juhl
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=3BC6E89A.BA8F98B6@bellsouth.net \
--to=ecprod@bellsouth.net \
--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 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.