From: Joerg Roedel <joro@8bytes.org>
To: bhelgaas@google.com
Cc: Shuah Khan <shuah.khan@hp.com>,
jiang.liu@huawei.com, shemminger@vyatta.com,
paulmck@linux.vnet.ibm.com, linasvepstas@gmail.com,
dhowells@redhat.com, davej@redhat.com, tglx@linutronix.de,
mtk.manpages@gmail.com, iommu@lists.linux-foundation.org,
linux-pci@vger.kernel.org, wangyijing@huawei.com,
LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH 0/4] pci: Add PCI_BUS() and PCI_DEVID() interfaces to return bus number and device id
Date: Wed, 13 Feb 2013 13:03:15 +0100 [thread overview]
Message-ID: <20130213120315.GE25591@8bytes.org> (raw)
In-Reply-To: <1360623614.2950.60.camel@lorien2>
Hi Bjorn,
On Mon, Feb 11, 2013 at 04:00:14PM -0700, Shuah Khan wrote:
> pci defines PCI_DEVFN(), PCI_SLOT(), and PCI_FUNC() interfaces, however,
> it doesn't have interfaces to return PCI bus and PCI device id. Drivers
> (AMD IOMMU, and AER) have module specific definitions for PCI_BUS() and
> AMD_IOMMU driver also has a module specific interface to calculate PCI
> device id from bus number and devfn.
>
> This patch set adds PCI_BUS(), and PCI_DEVID() to pci.h, changes are to
> use PCI_BUS() from pci. Changes AMD_IOMMU driver to use PCI_BUS() and
> PCI_DEVID() from pci.
Not sure who is going to merge this, it touches PCI and IOMMU code.
Personally I don't care :-) If you want to take it via your tree feel
free to add my
Reviewed-by: Joerg Roedel <joro@8bytes.org>
Tested-by: Joerg Roedel <joro@8bytes.org>
Acked-by: Joerg Roedel <joro@8bytes.org>
Otherwise please Ack the PCI parts and I will add it to my tree then.
Thanks,
Joerg
prev parent reply other threads:[~2013-02-13 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 23:00 [PATCH 0/4] pci: Add PCI_BUS() and PCI_DEVID() interfaces to return bus number and device id Shuah Khan
2013-02-13 12:03 ` Joerg Roedel [this message]
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=20130213120315.GE25591@8bytes.org \
--to=joro@8bytes.org \
--cc=bhelgaas@google.com \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jiang.liu@huawei.com \
--cc=linasvepstas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=shemminger@vyatta.com \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.com \
--cc=tglx@linutronix.de \
--cc=wangyijing@huawei.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 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).