LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Greg KH <gregkh@suse.de>
Cc: Matthew Wilcox <matthew@wil.cx>, Gary Hade <garyhade@us.ibm.com>,
	kaneshige.kenji@jp.fujitsu.com, warthog19@eaglescrag.net,
	kristen.c.accardi@intel.com, rick.jones2@hp.com,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	linux-acpi@vger.kernel.org
Subject: [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects
Date: Tue, 4 Mar 2008 17:42:52 -0700	[thread overview]
Message-ID: <20080305004252.GJ3694@ldl.fc.hp.com> (raw)

Hi Greg, all,

This is v8 of my "introduce pci_slot" series, to be considered for
inclusion in linux-next to get more test exposure and shake out
the bugs.

The major change in this revision is removing an earlier patch
which removed the 'path' sysfs attribute on SGI machines. After
review from Jesse Barnes and Prarit Bhargava, they kindly
informed me that 'path' is actually an SGI physical path, and not
a PCI address. My patch would have definitely broken userspace on
SGI machines, so I eliminated it, and 'path' remains on SGI boxes.

This brings the patch series down to a total of 3 patches:

	0001-Construct-one-fakephp-slot-per-pci-slot.patch
	0002-Introduce-pci_slot.patch
	0003-ACPI-PCI-slot-detection-driver.patch

Thanks for all the code reviews from various people.

I'm now just looking for some people to beat on this code and let
me know where I screwed up. :)

Thanks.

/ac


             reply	other threads:[~2008-03-05  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  0:42 Alex Chiang [this message]
2008-03-05  0:48 ` [PATCH 1/3] Construct one fakephp slot per pci slot Alex Chiang
2008-03-05  0:48 ` [PATCH 2/3] Introduce pci_slot Alex Chiang
2008-03-05  1:12   ` MUNEDA Takahiro
2008-03-05  0:49 ` [PATCH 3/3] ACPI PCI slot detection driver Alex Chiang
2008-03-05  4:47 ` [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects Greg KH
2008-03-06 17:49 ` Gary Hade

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=20080305004252.GJ3694@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=garyhade@us.ibm.com \
    --cc=gregkh@suse.de \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=rick.jones2@hp.com \
    --cc=warthog19@eaglescrag.net \
    --subject='Re: [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects' \
    /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

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).