From: Grant Grundler <grundler@parisc-linux.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Matthew Wilcox <willy@linux.intel.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Subject: Re: [PATCH 1/2] PCI/MSI: Introduce pci_msix_table_size()
Date: Sat, 24 Jan 2009 22:35:45 -0700 [thread overview]
Message-ID: <20090125053545.GC22539@colo.lackof.org> (raw)
In-Reply-To: <20090125052947.GB22539@colo.lackof.org>
On Sat, Jan 24, 2009 at 10:29:47PM -0700, Grant Grundler wrote:
> Is this intended to be used by drivers?
The answer depends on if "PCI Express port driver" can be loaded
as a module.
> If so, can you please add (a) corresponding documentation in
> either the MSI or pci.txt files and (b) EXPORT_SYMBOL_GPL?
>
> If not, can this declaration be static?
> (I haven't yet looked at the second patch...maybe this is obvious once
> I do.)
The answer seems to be no, it can't be static.
thanks,
grant
next prev parent reply other threads:[~2009-01-25 5:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:19 [PATCH 0/2] PCI/PCIe port driver: Fix allocation of interrupts Rafael J. Wysocki
2009-01-23 23:21 ` [PATCH 1/2] PCI/MSI: Introduce pci_msix_table_size() Rafael J. Wysocki
2009-01-25 5:29 ` Grant Grundler
2009-01-25 5:35 ` Grant Grundler [this message]
2009-01-25 19:01 ` Rafael J. Wysocki
2009-01-27 18:57 ` Jesse Barnes
2009-01-23 23:23 ` [PATCH 2/2] PCI/PCIe portdrv: Fix allocation of interrupts (rev. 6) Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 13:57 [PATCH] PCI PCIe portdrv: Fix allocation of interrupts (rev. 3) Rafael J. Wysocki
2009-01-19 9:00 ` [PATCH PCI PCIe portdrv: Fix allocation of interrupts (rev. 5) Kenji Kaneshige
2009-01-21 0:16 ` Rafael J. Wysocki
2009-01-21 0:18 ` [PATCH 1/2] PCI/MSI: Introduce pci_msix_table_size() Rafael J. Wysocki
2009-01-21 1:17 ` Hidetoshi Seto
2009-01-21 2:30 ` Michael Ellerman
2009-01-21 15:52 ` Rafael J. Wysocki
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=20090125053545.GC22539@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=willy@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox