From: Greg KH <gregkh@suse.de>
To: Alex Chiang <achiang@hp.com>, Matthew Wilcox <matthew@wil.cx>,
Gary Hade <garyhade@us.ibm.com>,
kaneshige.kenji@jp.fujitsu.com, warthog19@eaglescrag.net,
kristen.c.accardi@intel.com
Subject: Re: [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects
Date: Tue, 4 Mar 2008 20:47:10 -0800 [thread overview]
Message-ID: <20080305044710.GD22501@suse.de> (raw)
In-Reply-To: <20080305004252.GJ3694@ldl.fc.hp.com>
On Tue, Mar 04, 2008 at 05:42:52PM -0700, Alex Chiang wrote:
> 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.
Can you work with Kenji to get his approval on this before I add this to
the tree? It sounds like there are still some outstanding issues
getting this to work properly on his hardware. It needs to work without
relying on a module not being loaded, as the distros are never going to
go for that kind of solution.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Alex Chiang <achiang@hp.com>, 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: Re: [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects
Date: Tue, 4 Mar 2008 20:47:10 -0800 [thread overview]
Message-ID: <20080305044710.GD22501@suse.de> (raw)
In-Reply-To: <20080305004252.GJ3694@ldl.fc.hp.com>
On Tue, Mar 04, 2008 at 05:42:52PM -0700, Alex Chiang wrote:
> 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.
Can you work with Kenji to get his approval on this before I add this to
the tree? It sounds like there are still some outstanding issues
getting this to work properly on his hardware. It needs to work without
relying on a module not being loaded, as the distros are never going to
go for that kind of solution.
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-05 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 0:42 [PATCH 0/3, v8] PCI, ACPI: Physical PCI slot objects Alex Chiang
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 ` Greg KH [this message]
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=20080305044710.GD22501@suse.de \
--to=gregkh@suse.de \
--cc=achiang@hp.com \
--cc=garyhade@us.ibm.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=matthew@wil.cx \
--cc=warthog19@eaglescrag.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.