From: Matthew Wilcox <matthew@wil.cx>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Zhao, Yu" <yu.zhao@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Grant Grundler <grundler@parisc-linux.org>,
Alex Chiang <achiang@hp.com>, Roland Dreier <rdreier@cisco.com>,
Greg KH <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 3/6 v3] PCI: support ARI capability
Date: Thu, 2 Oct 2008 10:17:01 -0600 [thread overview]
Message-ID: <20081002161701.GO13822@parisc-linux.org> (raw)
In-Reply-To: <200810020903.16385.jbarnes@virtuousgeek.org>
On Thu, Oct 02, 2008 at 09:03:15AM -0700, Jesse Barnes wrote:
> Maybe we should be consistent with the other APIs and call it pci_enable_ari
> (like we do for wake & msi). Looks pretty good otherwise.
Those APIs are for drivers ... this is internal. I don't have any
objection of my own, though I agree with Alex's remark that the printk
is unnecessary and just adds clutter to the boot process.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-10-02 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 8:28 [PATCH 3/6 v3] PCI: support ARI capability Zhao, Yu
2008-09-30 22:31 ` Alex Chiang
2008-09-30 22:31 ` Alex Chiang
2008-10-02 16:03 ` Jesse Barnes
2008-10-02 16:17 ` Matthew Wilcox
2008-10-02 16:17 ` Matthew Wilcox [this message]
2008-10-08 2:56 ` Zhao, Yu
2008-10-08 2:56 ` Zhao, Yu
2008-10-02 16:03 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2008-09-27 8:28 Zhao, Yu
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=20081002161701.GO13822@parisc-linux.org \
--to=matthew@wil.cx \
--cc=achiang@hp.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rdreier@cisco.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yu.zhao@intel.com \
/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.