public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Hotplug PCI driver for 2.4.13-pre1
Date: Fri, 12 Oct 2001 11:31:14 -0700	[thread overview]
Message-ID: <20011012113114.A20602@kroah.com> (raw)

Hi,

Another release of the Compaq Hotplug PCI driver is available against
2.4.13-pre1 is at:
	http://www.kroah.com/linux/hotplug/pci-hotplug-2001_10_12-2.4.13-pre1.patch.gz
With a full changelog at:
	http://www.kroah.com/linux/hotplug/pci-hotplug-Changelog

The latest version of modutils is required to use this version of the
patch.

I have also included the ddfs patch from Pat Mochel in this patch, as
the hotplug pci driver now uses it as its interface to userspace.  I
have fixed a few minor bugs that I ran into in the ddfs patch, so people
interested in ddfs might want to take a look at this version.

Changes since the last release:
 	- forward ported to 2.4.13-pre1
	- changed the identifying feature of a hotplug pci slot from an
	  int to a char * due to the PPC hotplug pci driver's needs.
	- cleaned up the hotplug pci slot structure a bit to hid hotplug
	  pci core structures from the hotplug pci drivers.
 	- removed the last known direct hardware access code.  If anyone
	  sees any places that the Compaq driver does not use the proper
	  kernel apis to access hardware, please let me know.
	- removed all *_sleep_on() calls to eliminate the potential
	  races in those usages.
	
TODO:
	- move the filesystem code into the hotplug pci core, removing
	  it's dependency on the ddfs patch.
	- possibly merge the 2 passes of the pci bus when removing a
	  device as the /proc logic that required that is now gone.
	- Port the Linux PPC hotplug pci controller driver to the
	  hotplug pci core  interface, whenever Anton sends me an
	  updated file...

thanks,

greg k-h

                 reply	other threads:[~2001-10-12 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011012113114.A20602@kroah.com \
    --to=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