From: Andrew Morton <andrewm@uow.edu.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug TTD
Date: Fri, 12 Jan 2001 12:51:15 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97930350210631@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97901650309422@msgid-missing>
While I think of it. Something Linus said a few weeks back:
>
> 1: yenta driver sees the card insertion. schedules a call to
> pci_insert_device
We should actually change this, and do it only for the case where we don't
already have a driver for the device. If we have a driver fior the device,
we should assume that it is the drivers responsibility to notify the
system about higher-level events.
Does this really matter? We'll get a failed modprobe...
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-12 12:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 4:59 hotplug TTD Morton, Andrew [WOLL:4009-M:EXCH]
2001-01-09 5:47 ` Miles Lane
2001-01-09 6:55 ` Miles Lane
2001-01-09 8:49 ` Adam J. Richter
2001-01-09 17:09 ` David Brownell
2001-01-09 17:38 ` David Brownell
2001-01-10 6:20 ` Grover, Andrew
2001-01-10 6:34 ` Grover, Andrew
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:59 ` Andrew Morton
2001-01-11 16:10 ` David Brownell
2001-01-11 16:40 ` David Brownell
2001-01-11 17:18 ` David Hinds
2001-01-11 18:04 ` David Brownell
2001-01-12 0:09 ` Grover, Andrew
2001-01-12 0:33 ` Grover, Andrew
2001-01-12 1:13 ` Grover, Andrew
2001-01-12 12:51 ` Andrew Morton [this message]
2001-01-12 16:42 ` David Brownell
2001-01-12 17:37 ` David Brownell
2001-01-12 23:45 ` Keith Owens
2001-01-13 18:54 ` David Brownell
2001-01-13 23:25 ` Keith Owens
2001-02-03 23:37 ` Miles Lane
2001-02-03 23:48 ` Keith Owens
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=marc-linux-hotplug-97930350210631@msgid-missing \
--to=andrewm@uow.edu.au \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).