From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH net-next 0/8][pull request] Intel Wired LAN: Remove redundant Device Control Error Reporting Enable
Date: Tue, 31 Jan 2023 10:26:14 +0200 [thread overview]
Message-ID: <Y9jQpjLPkRR/emeH@unreal> (raw)
In-Reply-To: <20230130192519.686446-1-anthony.l.nguyen@intel.com>
On Mon, Jan 30, 2023 at 11:25:11AM -0800, Tony Nguyen wrote:
> Bjorn Helgaas says:
>
> Since f26e58bf6f54 ("PCI/AER: Enable error reporting when AER is native"),
> the PCI core sets the Device Control bits that enable error reporting for
> PCIe devices.
>
> This series removes redundant calls to pci_enable_pcie_error_reporting()
> that do the same thing from several NIC drivers.
>
> There are several more drivers where this should be removed; I started with
> just the Intel drivers here.
> ---
> TN: Removed mention of AER driver as this was taken through PCI tree [1]
> and fixed a typo.
>
> [1] https://lore.kernel.org/all/20230126231527.GA1322015@bhelgaas/
>
> The following are changes since commit 90e8ca0abb05ada6c1e2710eaa21688dafca26f2:
> Merge branch 'devlink-next'
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 10GbE
>
> Bjorn Helgaas (8):
> e1000e: Remove redundant pci_enable_pcie_error_reporting()
> fm10k: Remove redundant pci_enable_pcie_error_reporting()
> i40e: Remove redundant pci_enable_pcie_error_reporting()
> iavf: Remove redundant pci_enable_pcie_error_reporting()
> ice: Remove redundant pci_enable_pcie_error_reporting()
> igb: Remove redundant pci_enable_pcie_error_reporting()
> igc: Remove redundant pci_enable_pcie_error_reporting()
> ixgbe: Remove redundant pci_enable_pcie_error_reporting()
>
> drivers/net/ethernet/intel/e1000e/netdev.c | 7 -------
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c | 5 -----
> drivers/net/ethernet/intel/i40e/i40e_main.c | 4 ----
> drivers/net/ethernet/intel/iavf/iavf_main.c | 5 -----
> drivers/net/ethernet/intel/ice/ice_main.c | 3 ---
> drivers/net/ethernet/intel/igb/igb_main.c | 5 -----
> drivers/net/ethernet/intel/igc/igc_main.c | 5 -----
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 5 -----
> 8 files changed, 39 deletions(-)
I see that you didn't touch any other places except drivers/net/ethernet/intel/.
Are you planning to remove other occurrences too?
➜ kernel git:(rdma-next) git grep pci_enable_pcie_error_reporting -- drivers/infiniband/
drivers/infiniband/hw/hfi1/pcie.c: (void)pci_enable_pcie_error_reporting(pdev);
drivers/infiniband/hw/qib/qib_pcie.c: ret = pci_enable_pcie_error_reporting(pdev);
Thanks
>
> --
> 2.38.1
>
next prev parent reply other threads:[~2023-01-31 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 19:25 [PATCH net-next 0/8][pull request] Intel Wired LAN: Remove redundant Device Control Error Reporting Enable Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 1/8] e1000e: Remove redundant pci_enable_pcie_error_reporting() Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 2/8] fm10k: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 3/8] i40e: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 4/8] iavf: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 5/8] ice: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 6/8] igb: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 7/8] igc: " Tony Nguyen
2023-01-30 19:25 ` [PATCH net-next 8/8] ixgbe: " Tony Nguyen
2023-01-31 8:26 ` Leon Romanovsky [this message]
2023-01-31 18:05 ` [PATCH net-next 0/8][pull request] Intel Wired LAN: Remove redundant Device Control Error Reporting Enable Bjorn Helgaas
2023-02-01 8:23 ` Leon Romanovsky
2023-02-01 5:10 ` 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=Y9jQpjLPkRR/emeH@unreal \
--to=leon@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).