From: Ian Cowan <ian@linux.cowan.aero>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Cowan <ian@linux.cowan.aero>
Subject: [PATCH 3/3] PCI: SHPC: update todo
Date: Sat, 12 Nov 2022 09:28:59 -0500 [thread overview]
Message-ID: <20221112142859.319733-4-ian@linux.cowan.aero> (raw)
In-Reply-To: <20221112142859.319733-1-ian@linux.cowan.aero>
This removes the note in the todo regarding the removal of the
->get_mode1_ECC_cap callback.
Signed-off-by: Ian Cowan <ian@linux.cowan.aero>
---
drivers/pci/hotplug/TODO | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/pci/hotplug/TODO b/drivers/pci/hotplug/TODO
index 88f217c82b4f..fdb8dd6ea24d 100644
--- a/drivers/pci/hotplug/TODO
+++ b/drivers/pci/hotplug/TODO
@@ -58,9 +58,6 @@ shpchp:
pciehp with commit 82a9e79ef132 ("PCI: pciehp: remove hpc_ops"). Clarify
if there was a specific reason not to apply the same change to shpchp.
-* The ->get_mode1_ECC_cap callback in shpchp_hpc_ops is never invoked.
- Why was it introduced? Can it be removed?
-
* The hardirq handler shpc_isr() queues events on a workqueue. It can be
simplified by converting it to threaded IRQ handling. Use pciehp as a
template.
--
2.38.1
next prev parent reply other threads:[~2022-11-12 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 14:28 [PATCH 0/3] PCI: SHPC: removed unused get_mode1_ECC_cap callback Ian Cowan
2022-11-12 14:28 ` [PATCH 1/3] PCI: SHPC: remove unused get_mode1_ECC_cap callback declaration Ian Cowan
2022-11-12 14:28 ` [PATCH 2/3] PCI: SHPC: remove unused get_mode1_ECC_cap callback from definition Ian Cowan
2022-11-12 14:28 ` Ian Cowan [this message]
2022-12-07 14:37 ` [PATCH 0/3] PCI: SHPC: removed unused get_mode1_ECC_cap callback 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=20221112142859.319733-4-ian@linux.cowan.aero \
--to=ian@linux.cowan.aero \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.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).