From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: pci_lost_interrupt still needed?
Date: Tue, 28 Jul 2020 22:28:08 +0200 [thread overview]
Message-ID: <63322b3a-3fae-2437-8359-e6f32bede850@gmail.com> (raw)
In-Reply-To: <20200728202126.GA1859314@bjorn-Precision-5520>
On 28.07.2020 22:21, Bjorn Helgaas wrote:
> On Tue, Jul 28, 2020 at 09:20:34PM +0200, Heiner Kallweit wrote:
>> Seems that pci_lost_interrupt() has no user. Do we still need this function?
>> Same applies for related enum pci_lost_interrupt_reason.
>
> If there's no user, remove it. Bonus points if you look up the
> removal of the last use.
>
It was introduced in 2.6.27, and apparently there never has been a single user.
So I'll submit a patch to remove it.
next prev parent reply other threads:[~2020-07-28 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 19:20 pci_lost_interrupt still needed? Heiner Kallweit
2020-07-28 20:21 ` Bjorn Helgaas
2020-07-28 20:28 ` Heiner Kallweit [this message]
2020-07-28 20:50 ` 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=63322b3a-3fae-2437-8359-e6f32bede850@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@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).