From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adam Belay <abelay@novell.com>
Cc: Greg KH <greg@kroah.com>, rml@novell.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] add driver matching priorities
Date: Thu, 10 Feb 2005 18:45:08 +0000 [thread overview]
Message-ID: <20050210184508.B5800@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1108055918.3423.23.camel@localhost.localdomain>; from abelay@novell.com on Thu, Feb 10, 2005 at 12:18:37PM -0500
On Thu, Feb 10, 2005 at 12:18:37PM -0500, Adam Belay wrote:
> > I think the issue that Al raises about drivers grabbing devices, and
> > then trying to unbind them might be a real problem.
>
> I agree. Do you think registering every in-kernel driver before probing
> hardware would solve this problem?
In which case, consider whether we should be tainting the kernel if
someone loads a device driver, it binds to a device, and then they
unload that driver.
It's precisely the same situation, and precisely the same mechanics
as what I've suggested should be going on here. If one scenario is
inherently buggy, so is the other.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2005-02-10 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 22:30 [RFC][PATCH] add driver matching priorities Adam Belay
2005-01-28 23:23 ` Dmitry Torokhov
2005-01-28 23:33 ` Adam Belay
2005-01-28 23:51 ` Dmitry Torokhov
2005-01-29 0:05 ` Adam Belay
2005-01-29 0:11 ` Al Viro
2005-01-29 2:45 ` Dmitry Torokhov
2005-02-10 8:41 ` Greg KH
2005-02-10 17:18 ` Adam Belay
2005-02-10 18:08 ` Dmitry Torokhov
2005-02-10 18:12 ` Greg KH
2005-02-10 21:26 ` Adam Belay
2005-02-10 18:33 ` Greg KH
2005-02-10 18:46 ` Dmitry Torokhov
2005-02-10 21:32 ` Adam Belay
2005-02-10 18:45 ` Russell King [this message]
2005-02-10 21:37 ` Adam Belay
2005-02-25 23:41 ` Greg KH
2005-03-01 0:05 ` Adam Belay
2005-03-01 7:58 ` Greg KH
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=20050210184508.B5800@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=abelay@novell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
/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