From: Dave Jones <davej@codemonkey.org.uk>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI changes for 2.5.69
Date: Thu, 22 May 2003 23:36:16 +0100 [thread overview]
Message-ID: <20030522223616.GA5830@suse.de> (raw)
In-Reply-To: <10536411591193@kroah.com>
On Thu, May 22, 2003 at 03:05:59PM -0700, Greg KH wrote:
> One may write new PCI device IDs into the new_id file:
> echo "8086 1229" > new_id
>
> which will cause a new device ID (sysfs name 0) to be added to the driver.
Why not call the probe routine at this point ?
This would do away with the need for the probe_it file.
The only downside I can see is that if we have a script
echoing lots of device id updates, we're going to lots of
additional (-ENODEV) probes.
Dave
next prev parent reply other threads:[~2003-05-22 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 22:02 [BK PATCH] PCI changes for 2.5.69 Greg KH
2003-05-22 22:05 ` [PATCH] " Greg KH
2003-05-22 22:05 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-23 6:07 ` Christoph Hellwig
2003-05-23 7:02 ` Greg KH
2003-05-22 22:36 ` Dave Jones [this message]
2003-05-22 22:48 ` 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=20030522223616.GA5830@suse.de \
--to=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--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