Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ian Cowan <ian@linux.cowan.aero>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] PCI: SHPC: removed unused get_mode1_ECC_cap callback
Date: Wed, 7 Dec 2022 08:37:06 -0600	[thread overview]
Message-ID: <20221207143706.GA1441026@bhelgaas> (raw)
In-Reply-To: <20221112142859.319733-1-ian@linux.cowan.aero>

On Sat, Nov 12, 2022 at 09:28:56AM -0500, Ian Cowan wrote:
> In the SHPC module, the get_mode1_ECC_cap callback is never used from
> the hpc_ops struct, so this patch series removes that callback from both the
> definition of the struct and the definition of the shpchp_hps_ops
> struct. Additionally, this removes the reference in the TODO of the SHPC
> module.
> 
> Ian Cowan (3):
>   PCI: SHPC: remove unused get_mode1_ECC_cap callback declaration
>   PCI: SHPC: remove unused get_mode1_ECC_cap callback from definition
>   PCI: SHPC: update todo
> 
>  drivers/pci/hotplug/TODO         |  3 ---
>  drivers/pci/hotplug/shpchp.h     |  1 -
>  drivers/pci/hotplug/shpchp_hpc.c | 18 ------------------
>  3 files changed, 22 deletions(-)

Applied to pci/hotplug for v6.2, thanks, Ian!

      parent reply	other threads:[~2022-12-07 14:37 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 ` [PATCH 3/3] PCI: SHPC: update todo Ian Cowan
2022-12-07 14:37 ` 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=20221207143706.GA1441026@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=ian@linux.cowan.aero \
    --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