Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next 2/3] igc: Remove unused igc_read/write_pci_cfg wrappers
Date: Sun, 5 Jan 2025 11:01:46 +0200	[thread overview]
Message-ID: <8bc2fccd-e367-6049-3623-3ffef7e56af7@intel.com> (raw)
In-Reply-To: <20250102174142.200700-3-linux@treblig.org>



On 1/2/2025 7:41 PM, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> igc_read_pci_cfg() and igc_write_pci_cfg were added in 2018 as part of
> commit 146740f9abc4 ("igc: Add support for PF")
> but have remained unused.
> 
> Remove them.
> 
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>

Reviewed-by: Vitaly Lifshits <vitaly.lifshits@intel.com>

> ---
>   drivers/net/ethernet/intel/igc/igc_hw.h   |  2 --
>   drivers/net/ethernet/intel/igc/igc_main.c | 14 --------------
>   2 files changed, 16 deletions(-)
> 
> diff --git a/drivers/net/ethernet/intel/igc/igc_hw.h b/drivers/net/ethernet/intel/igc/igc_hw.h
> index d9d1a1a11daf..7ec7e395020b 100644
> --- a/drivers/net/ethernet/intel/igc/igc_hw.h
> +++ b/drivers/net/ethernet/intel/igc/igc_hw.h
> @@ -281,7 +281,5 @@ struct net_device *igc_get_hw_dev(struct igc_hw *hw);
>   
>   s32  igc_read_pcie_cap_reg(struct igc_hw *hw, u32 reg, u16 *value);
>   s32  igc_write_pcie_cap_reg(struct igc_hw *hw, u32 reg, u16 *value);
> -void igc_read_pci_cfg(struct igc_hw *hw, u32 reg, u16 *value);
> -void igc_write_pci_cfg(struct igc_hw *hw, u32 reg, u16 *value);
>   
>   #endif /* _IGC_HW_H_ */
> diff --git a/drivers/net/ethernet/intel/igc/igc_main.c b/drivers/net/ethernet/intel/igc/igc_main.c
> index 27872bdea9bd..9c92673a7240 100644
> --- a/drivers/net/ethernet/intel/igc/igc_main.c
> +++ b/drivers/net/ethernet/intel/igc/igc_main.c
> @@ -6780,20 +6780,6 @@ static const struct net_device_ops igc_netdev_ops = {
>   };
>   
>   /* PCIe configuration access */
> -void igc_read_pci_cfg(struct igc_hw *hw, u32 reg, u16 *value)
> -{
> -	struct igc_adapter *adapter = hw->back;
> -
> -	pci_read_config_word(adapter->pdev, reg, value);
> -}
> -
> -void igc_write_pci_cfg(struct igc_hw *hw, u32 reg, u16 *value)
> -{
> -	struct igc_adapter *adapter = hw->back;
> -
> -	pci_write_config_word(adapter->pdev, reg, *value);
> -}
> -
>   s32 igc_read_pcie_cap_reg(struct igc_hw *hw, u32 reg, u16 *value)
>   {
>   	struct igc_adapter *adapter = hw->back;
> 

  reply	other threads:[~2025-01-05  9:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 17:41 [Intel-wired-lan] [PATCH net-next 0/3] igc deadcoding linux
2025-01-02 17:41 ` [Intel-wired-lan] [PATCH net-next 1/3] igc: Remove unused igc_acquire/release_nvm linux
2025-01-05  9:01   ` Lifshits, Vitaly
2025-01-02 17:41 ` [Intel-wired-lan] [PATCH net-next 2/3] igc: Remove unused igc_read/write_pci_cfg wrappers linux
2025-01-05  9:01   ` Lifshits, Vitaly [this message]
2025-01-02 17:41 ` [Intel-wired-lan] [PATCH net-next 3/3] igc: Remove unused igc_read/write_pcie_cap_reg linux
2025-01-05  9:02   ` Lifshits, Vitaly
2025-01-06 18:44 ` [Intel-wired-lan] [PATCH net-next 0/3] igc deadcoding Tony Nguyen
2025-01-06 21:50 ` patchwork-bot+netdevbpf

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=8bc2fccd-e367-6049-3623-3ffef7e56af7@intel.com \
    --to=vitaly.lifshits@intel.com \
    --cc=intel-wired-lan@osuosl.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