From: Nico Schottelius <nicos@pcsystems.de>
To: Philip Blundell <philb@gnu.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: parport problems with devfs
Date: Wed, 16 May 2001 15:33:31 +0200 [thread overview]
Message-ID: <3B0281AB.10B6BD4E@pcsystems.de> (raw)
In-Reply-To: <3B027E46.5095E8BB@pcsystems.de> <E1501Og-0007EH-00@kings-cross.london.uk.eu.org>
Hmm..seems you are exactly right!
Sorry for that wrong though!
Nico
Philip Blundell wrote:
> >I attached the problem occured with parport and devfs.
> >I don't exactly know where the problem in the parport source
> >is. If someone has a patch for it, I will test it.
>
> I don't think this is a bug. You need to load the `lp' module.
>
> p.
next prev parent reply other threads:[~2001-05-16 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 13:19 parport problems with devfs Nico Schottelius
2001-05-16 13:31 ` Philip Blundell
2001-05-16 13:33 ` Nico Schottelius [this message]
2001-05-21 19:09 ` Anuradha Ratnaweera
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=3B0281AB.10B6BD4E@pcsystems.de \
--to=nicos@pcsystems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=philb@gnu.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.