From: David Howells <dhowells@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: dhowells@redhat.com, shuah.khan@hp.com,
Joerg Roedel <joro@8bytes.org>,
paulmck@linux.vnet.ibm.com, linasvepstas@gmail.com,
davej@redhat.com, tglx@linutronix.de, mtk.manpages@gmail.com,
iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, shemminger@vyatta.com,
jiang.liu@huawei.com, wangyijing@huawei.com, shuahkhan@gmail.com
Subject: Re: [PATCH 1/4] pci: Add PCI_BUS() and PCI_DEVID() interfaces to return bus number and device id
Date: Tue, 26 Feb 2013 00:45:40 +0000 [thread overview]
Message-ID: <19586.1361839540@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAErSpo6jY1bX9G59uz8Zt_pDJ4OoR=kJkGjNLYYRTrKVXM8+eg@mail.gmail.com>
Bjorn Helgaas <bhelgaas@google.com> wrote:
> David, can you point me at a description of include/uapi ... what is
> there and why, and how we should decide what new things go in
> include/uapi/linux/pci.h as opposed to include/linux/pci.h? Maybe
> there should be something in Documentation/?
Probably in CodingStyle, Submitting* or somewhere similar.
> I'm guessing it's something to do with being exported to userland, but
> I'm not sure the things in this patch (PCI_DEV_ID, PCI_BUS) are really
> exportable in the sense of being used for syscalls, etc.
As a rule, if it's in uapi/ then it's exported to userspace; if it's not, then
it isn't. The old headers where disintegrated along the lines of __KERNEL__
delimited sections by my scripts.
David
next prev parent reply other threads:[~2013-02-26 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 23:00 [PATCH 1/4] pci: Add PCI_BUS() and PCI_DEVID() interfaces to return bus number and device id Shuah Khan
2013-02-21 1:19 ` Bjorn Helgaas
2013-02-25 16:37 ` Shuah Khan
2013-02-25 21:23 ` Bjorn Helgaas
2013-02-25 21:53 ` Shuah Khan
2013-02-27 21:48 ` Shuah Khan
2013-02-26 0:45 ` David Howells [this message]
2013-02-25 21:28 ` Bjorn Helgaas
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=19586.1361839540@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=bhelgaas@google.com \
--cc=davej@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jiang.liu@huawei.com \
--cc=joro@8bytes.org \
--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