Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
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 15:21:26 -0500	[thread overview]
Message-ID: <20200728202126.GA1859314@bjorn-Precision-5520> (raw)
In-Reply-To: <f5eba931-6e27-8f50-d018-7d51a983bfb8@gmail.com>

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.

  reply	other threads:[~2020-07-28 20:21 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 [this message]
2020-07-28 20:28   ` Heiner Kallweit
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=20200728202126.GA1859314@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=hkallweit1@gmail.com \
    --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