From: Reinette Chatre <reinette.chatre@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <bhelgaas@google.com>, <nathan@kernel.org>,
<ndesaulniers@google.com>, <trix@redhat.com>,
<tglx@linutronix.de>, <kevin.tian@intel.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>
Subject: Re: [PATCH] PCI/MSI: Provide stubs for IMS functions
Date: Wed, 18 Oct 2023 10:03:07 -0700 [thread overview]
Message-ID: <943c50fe-b951-4e5e-b130-64e20742a3c2@intel.com> (raw)
In-Reply-To: <20231018165231.GA1365828@bhelgaas>
On 10/18/2023 9:52 AM, Bjorn Helgaas wrote:
> On Wed, Oct 18, 2023 at 11:43:51AM -0500, Bjorn Helgaas wrote:
>> On Tue, Oct 17, 2023 at 10:56:38AM -0700, Reinette Chatre wrote:
>>> The IMS related functions (pci_create_ims_domain(),
>>> pci_ims_alloc_irq(), and pci_ims_free_irq()) are not declared
>>> when CONFIG_PCI_MSI is disabled.
>>>
>>> Provide definitions of these functions for use when callers
>>> are compiled with CONFIG_PCI_MSI disabled.
>>>
>>> Fixes: 0194425af0c8 ("PCI/MSI: Provide IMS (Interrupt Message Store) support")
>>> Fixes: c9e5bea27383 ("PCI/MSI: Provide pci_ims_alloc/free_irq()")
>>> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
>>> Cc: stable@vger.kernel.org # v6.2+
>>
>> Applied to pci/misc for v6.7, thanks!
>
> And dropped, since Thomas applied it via -tip:
> https://git.kernel.org/tip/41efa431244f6498833ff8ee8dde28c4924c5479
>
Thank you very much.
Reinette
prev parent reply other threads:[~2023-10-18 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 17:56 [PATCH] PCI/MSI: Provide stubs for IMS functions Reinette Chatre
2023-10-18 16:43 ` Bjorn Helgaas
2023-10-18 16:52 ` Bjorn Helgaas
2023-10-18 17:03 ` Reinette Chatre [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=943c50fe-b951-4e5e-b130-64e20742a3c2@intel.com \
--to=reinette.chatre@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=tglx@linutronix.de \
--cc=trix@redhat.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