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 2/3] PCI: SHPC: remove unused get_mode1_ECC_cap callback from definition
Date: Sat, 12 Nov 2022 09:28:58 -0500 [thread overview]
Message-ID: <20221112142859.319733-3-ian@linux.cowan.aero> (raw)
In-Reply-To: <20221112142859.319733-1-ian@linux.cowan.aero>
The ->get_mode1_ECC_cap callback is never used in the shpchp_hpc_ops
struct, so we can remove that. This removes that from the hpc_ops struct
definition in the shpc module.
Signed-off-by: Ian Cowan <ian@linux.cowan.aero>
---
drivers/pci/hotplug/shpchp.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/pci/hotplug/shpchp.h b/drivers/pci/hotplug/shpchp.h
index 6e85885b554c..3a97f455336e 100644
--- a/drivers/pci/hotplug/shpchp.h
+++ b/drivers/pci/hotplug/shpchp.h
@@ -311,7 +311,6 @@ struct hpc_ops {
int (*get_latch_status)(struct slot *slot, u8 *status);
int (*get_adapter_status)(struct slot *slot, u8 *status);
int (*get_adapter_speed)(struct slot *slot, enum pci_bus_speed *speed);
- int (*get_mode1_ECC_cap)(struct slot *slot, u8 *mode);
int (*get_prog_int)(struct slot *slot, u8 *prog_int);
int (*query_power_fault)(struct slot *slot);
void (*green_led_on)(struct slot *slot);
--
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 ` Ian Cowan [this message]
2022-11-12 14:28 ` [PATCH 3/3] PCI: SHPC: update todo Ian Cowan
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-3-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).