From: linux@treblig.org
To: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH net-next 0/3] igc deadcoding
Date: Thu, 2 Jan 2025 17:41:39 +0000 [thread overview]
Message-ID: <20250102174142.200700-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
Hi,
This set removes some functions that are entirely unused
and have been since ~2018.
Build tested.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
(Repost now netdev is open)
Dr. David Alan Gilbert (3):
igc: Remove unused igc_acquire/release_nvm
igc: Remove unused igc_read/write_pci_cfg wrappers
igc: Remove unused igc_read/write_pcie_cap_reg
drivers/net/ethernet/intel/igc/igc_hw.h | 5 ---
drivers/net/ethernet/intel/igc/igc_main.c | 39 ------------------
drivers/net/ethernet/intel/igc/igc_nvm.c | 50 -----------------------
drivers/net/ethernet/intel/igc/igc_nvm.h | 2 -
4 files changed, 96 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-02 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 17:41 linux [this message]
2025-01-02 17:41 ` [PATCH net-next 1/3] igc: Remove unused igc_acquire/release_nvm linux
2025-01-02 17:41 ` [PATCH net-next 2/3] igc: Remove unused igc_read/write_pci_cfg wrappers linux
2025-01-02 17:41 ` [PATCH net-next 3/3] igc: Remove unused igc_read/write_pcie_cap_reg linux
2025-01-06 18:44 ` [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=20250102174142.200700-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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).