From: Frans Pop <elendil@planet.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parport: quickfix the proc registration bug
Date: Wed, 3 Jun 2009 23:20:11 +0200 [thread overview]
Message-ID: <200906032320.11870.elendil@planet.nl> (raw)
In-Reply-To: <20090602155718.12461.87554.stgit@t61.ukuu.org.uk>
Alan Cox wrote:
> Ideally we should have a directory of drivers and a link to the 'active'
> driver. For now just show the first device which is effectively the
> existing semantics without a warning.
>
> This is an update on the original buggy patch that I then forgot to
> resubmit. Confusingly it was proposed by Red Hat, written by Etched
> Pixels fixed and submitted by Intel ...
>
> Resolves-Bug: http://bugzilla.kernel.org/show_bug.cgi?id=9749
> Signed-off-by: Alan Cox <alan@linux.intel.com>
Thanks Alan. Unfortunately I'm no longer able to test this as my printer
is now connected via USB to my notebook's docking station instead of via
a parport to my desktop (which was prompted to home server and moved to a
different room).
prev parent reply other threads:[~2009-06-03 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 15:58 Alan Cox
2009-06-03 21:20 ` Frans Pop [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=200906032320.11870.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®