From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] PCI/MSI: Remove unused interfaces
Date: Wed, 27 Mar 2019 08:58:48 -0500 [thread overview]
Message-ID: <20190327135848.GA24180@google.com> (raw)
In-Reply-To: <20190325221229.36930-1-helgaas@kernel.org>
[+cc Lorenzo, Michal, linux-arm-kernel]
On Mon, Mar 25, 2019 at 05:12:27PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> pcie-xilinx-nwl.c is the only driver to use mask_msi_irq() and
> unmask_msi_irq(), which are trivial wrappers around PCI-specific functions.
> We obviously know we need the PCI versions in this driver, so use them
> directly, as all the other PCI host controller drivers do, and remove the
> unused wrappers.
>
> Unless there's objection, I'll merge both of these via my tree just to keep
> them together.
These are on pci/msi for v5.2.
> Bjorn Helgaas (2):
> PCI/MSI: Remove unused __write_msi_msg() and write_msi_msg()
> PCI/MSI: Remove unused mask_msi_irq() and unmask_msi_irq()
>
> drivers/pci/controller/pcie-xilinx-nwl.c | 9 ++++-----
> include/linux/msi.h | 18 ------------------
> 2 files changed, 4 insertions(+), 23 deletions(-)
>
> --
> 2.21.0.392.gf8f6787159e-goog
>
prev parent reply other threads:[~2019-03-27 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 22:12 [PATCH 0/2] PCI/MSI: Remove unused interfaces Bjorn Helgaas
2019-03-25 22:12 ` [PATCH 1/2] PCI/MSI: Remove unused __write_msi_msg() and write_msi_msg() Bjorn Helgaas
2019-03-25 22:12 ` [PATCH 2/2] PCI/MSI: Remove unused mask_msi_irq() and unmask_msi_irq() Bjorn Helgaas
2019-03-27 13:58 ` Bjorn Helgaas [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=20190327135848.GA24180@google.com \
--to=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=michal.simek@xilinx.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;
as well as URLs for NNTP newsgroup(s).