From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Kevin Tian <kevin.tian@intel.com>, Marc Zyngier <maz@kernel.org>,
Reinette Chatre <reinette.chatre@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>,
Dave Jiang <dave.jiang@intel.com>,
Megha Dey <megha.dey@intel.com>,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/3] PCI/MSI: Remove IMS (Interrupt Message Store) support for now
Date: Mon, 1 Apr 2024 18:23:23 -0500 [thread overview]
Message-ID: <20240401232326.1794707-1-helgaas@kernel.org> (raw)
In-Reply-To: <e5bacec0-28ca-4cd9-9ffe-92feaf5fbfef@kernel.org>
From: Bjorn Helgaas <bhelgaas@google.com>
IMS (Interrupt Message Store) support appeared in v6.2, but there are no
users yet.
Remove it for now. We can add it back when a user comes along.
Bjorn Helgaas (3):
Revert "PCI/MSI: Provide stubs for IMS functions"
Revert "PCI/MSI: Provide pci_ims_alloc/free_irq()"
Revert "PCI/MSI: Provide IMS (Interrupt Message Store) support"
drivers/pci/msi/api.c | 50 -------------------------------
drivers/pci/msi/irqdomain.c | 59 -------------------------------------
include/linux/pci.h | 26 ----------------
3 files changed, 135 deletions(-)
--
2.34.1
next parent reply other threads:[~2024-04-01 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e5bacec0-28ca-4cd9-9ffe-92feaf5fbfef@kernel.org>
2024-04-01 23:23 ` Bjorn Helgaas [this message]
2024-04-01 23:23 ` [PATCH 1/3] Revert "PCI/MSI: Provide stubs for IMS functions" Bjorn Helgaas
2024-04-02 2:46 ` Tian, Kevin
2024-04-01 23:23 ` [PATCH 2/3] Revert "PCI/MSI: Provide pci_ims_alloc/free_irq()" Bjorn Helgaas
2024-04-02 2:47 ` Tian, Kevin
2024-04-01 23:23 ` [PATCH 3/3] Revert "PCI/MSI: Provide IMS (Interrupt Message Store) support" Bjorn Helgaas
2024-04-02 2:48 ` Tian, Kevin
2024-04-02 2:45 ` [PATCH 0/3] PCI/MSI: Remove IMS (Interrupt Message Store) support for now Tian, Kevin
2024-04-02 16:42 ` 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=20240401232326.1794707-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maz@kernel.org \
--cc=megha.dey@intel.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
/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