linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
	kvm@vger.kernel.org, alex.williamson@redhat.com,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI: Export MSI message relevant functions
Date: Fri, 5 Sep 2014 10:15:55 +1000	[thread overview]
Message-ID: <20140905001555.GA9963@shangw> (raw)
In-Reply-To: <20140904225736.GJ17125@google.com>

On Thu, Sep 04, 2014 at 04:57:36PM -0600, Bjorn Helgaas wrote:
>On Mon, May 19, 2014 at 01:01:07PM +1000, Gavin Shan wrote:
>> The patch exports 2 MSI message relevant functions, which will be
>> used by VFIO PCI driver. The VFIO PCI driver would be built as
>> a module.
>> 
>> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>
>Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
>I think Alex will merge this along with the other ones.  Sorry this
>took so long.  I don't really like this, but I just can't figure out
>any solution that's better.
>

Thanks, Bjorn. I thought you must forget this. Lets get it in firstly
and I'll do more investigation later to see if I can figure out something
better.

Thanks,
Gavin

>> ---
>>  drivers/pci/msi.c | 2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
>> index 955ab79..2350271 100644
>> --- a/drivers/pci/msi.c
>> +++ b/drivers/pci/msi.c
>> @@ -324,6 +324,7 @@ void get_cached_msi_msg(unsigned int irq, struct msi_msg *msg)
>>  
>>  	__get_cached_msi_msg(entry, msg);
>>  }
>> +EXPORT_SYMBOL_GPL(get_cached_msi_msg);
>>  
>>  void __write_msi_msg(struct msi_desc *entry, struct msi_msg *msg)
>>  {
>> @@ -368,6 +369,7 @@ void write_msi_msg(unsigned int irq, struct msi_msg *msg)
>>  
>>  	__write_msi_msg(entry, msg);
>>  }
>> +EXPORT_SYMBOL_GPL(write_msi_msg);
>>  
>>  static void free_msi_irqs(struct pci_dev *dev)
>>  {
>> -- 
>> 1.8.3.2
>> 
>


  reply	other threads:[~2014-09-05  0:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19  3:01 [PATCH 0/4] VFIO Misc fixes Gavin Shan
2014-05-19  3:01 ` [PATCH 1/4] PCI: Export MSI message relevant functions Gavin Shan
2014-05-22  5:10   ` Gavin Shan
2014-09-04 22:57   ` Bjorn Helgaas
2014-09-05  0:15     ` Gavin Shan [this message]
2014-05-19  3:01 ` [PATCH 2/4] drivers/vfio: Rework offsetofend() Gavin Shan
2014-05-19  3:01 ` [PATCH 3/4] drivers/vfio/pci: Fix wrong MSI interrupt count Gavin Shan
2014-05-19  3:01 ` [PATCH 4/4] vfio/pci: Restore MSIx message prior to enabling Gavin Shan
2014-05-30 22:12   ` Bjorn Helgaas
2014-05-31 11:42     ` Gavin Shan
2014-06-02 16:57       ` Bjorn Helgaas
2014-06-05  5:51         ` Gavin Shan
2014-09-10  8:13   ` Gavin Shan
2014-09-26  3:19     ` Gavin Shan
2014-09-26  3:46       ` Alex Williamson
2014-09-27  5:33         ` Gavin Shan
2014-05-19 21:37 ` [PATCH 0/4] VFIO Misc fixes Alex Williamson
2014-05-30 21:06   ` Alex Williamson
  -- strict thread matches above, loose matches on Subject: below --
2014-05-13  1:35 [PATCH v2 " Gavin Shan
2014-05-13  1:35 ` [PATCH 1/4] PCI: Export MSI message relevant functions Gavin Shan

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=20140905001555.GA9963@shangw \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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).