From: David Woodhouse <dwmw2@infradead.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Thomas Hood <jdthood@mail.com>, Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parport_pc to use pnpbios_register_driver()
Date: Wed, 14 Nov 2001 10:17:17 +0000 [thread overview]
Message-ID: <15273.1005733037@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111140935350.791-100000@vaio>
In-Reply-To: <Pine.LNX.4.33.0111140935350.791-100000@vaio>
kai@tp1.ruhr-uni-bochum.de said:
> BTW: I think the current logic is useful, as it allows the user to
> specify in the beginning that he doesn't have an ISA/ISAPNP bus and
> thus gets never asked for drivers/features he couldn't possibly use.
> But that may be a matter of taste, and I believe CML2 allows for
> both.
Then the first set of CML2 rules which get merged should not be changing
the behaviour of such things - they should be looked at later. The first
merge of CML2 should have rules which _exactly_ match the existing
behaviour of CML1.
--
dwmw2
next prev parent reply other threads:[~2001-11-14 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 5:36 [PATCH] parport_pc to use pnpbios_register_driver() Thomas Hood
[not found] ` <200111102104.fAAL4pk19362@spf4.us4.outblaze.com>
2001-11-11 4:52 ` [PATCH] parport_pc to use pnpbios_register_driver() #2 Thomas Hood
2001-11-11 20:42 ` [PATCH] parport_pc to use pnpbios_register_driver() Kai Germaschewski
2001-11-12 1:56 ` Keith Owens
2001-11-12 8:30 ` Kai Germaschewski
2001-11-13 21:41 ` Thomas Hood
2001-11-14 9:25 ` Kai Germaschewski
2001-11-14 10:17 ` David Woodhouse [this message]
2001-11-14 15:46 ` Thomas Hood
2001-11-15 13:30 ` [PATCH] parport_pc to use pnpbios_register_driver() #4 Thomas Hood
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=15273.1005733037@redhat.com \
--to=dwmw2@infradead.org \
--cc=jdthood@mail.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kaos@ocs.com.au \
--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.