From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
nic_swsd@realtek.com, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v4 0/3] PCI: Disable parity checking
Date: Wed, 31 Mar 2021 13:08:56 +0200 [thread overview]
Message-ID: <3ed9ff5a-3984-1abd-c857-dd5ca942fcde@gmail.com> (raw)
In-Reply-To: <20210330174318.1289680-1-helgaas@kernel.org>
On 30.03.2021 19:43, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> I think this is essentially the same as Heiner's v3 posting, with these
> changes:
>
> - Added a pci_disable_parity() interface in pci.c instead of making a
> public pci_quirk_broken_parity() because quirks.c is only compiled when
> CONFIG_PCI_QUIRKS=y.
>
> - Removed the setting of dev->broken_parity_status because it's really
> only used by EDAC error reporting, and if we disable parity error
> reporting, we shouldn't get there. This change will be visible in the
> sysfs "broken_parity_status" file, but I doubt that's important.
>
> I dropped Leon's reviewed-by because I fiddled with the code. Similarly I
> haven't added your signed-off-by, Heiner, because I don't want you blamed
> for my errors. But if this looks OK to you I'll add it.
>
> v1: https://lore.kernel.org/r/a6f09e1b-4076-59d1-a4e3-05c5955bfff2@gmail.com
> v2: https://lore.kernel.org/r/bbc33d9b-af7c-8910-cdb3-fa3e3b2e3266@gmail.com
> - reduce scope of N2100 change to using the new PCI core quirk
> v3: https://lore.kernel.org/r/992c800e-2e12-16b0-4845-6311b295d932@gmail.com/
> - improve commit message of patch 2
>
> v4:
> - add pci_disable_parity() (not conditional on CONFIG_PCI_QUIRKS)
> - remove setting of dev->broken_parity_status
>
>
> Bjorn Helgaas (1):
> PCI: Add pci_disable_parity()
>
> Heiner Kallweit (2):
> IB/mthca: Disable parity reporting
> ARM: iop32x: disable N2100 PCI parity reporting
>
> arch/arm/mach-iop32x/n2100.c | 8 ++++----
> drivers/net/ethernet/realtek/r8169_main.c | 14 --------------
> drivers/pci/pci.c | 17 +++++++++++++++++
> drivers/pci/quirks.c | 13 ++++---------
> include/linux/pci.h | 1 +
> 5 files changed, 26 insertions(+), 27 deletions(-)
>
LGTM. Thanks!
next prev parent reply other threads:[~2021-03-31 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 17:43 [PATCH v4 0/3] PCI: Disable parity checking Bjorn Helgaas
2021-03-30 17:43 ` [PATCH v4 1/3] PCI: Add pci_disable_parity() Bjorn Helgaas
2021-03-30 17:43 ` [PATCH v4 2/3] IB/mthca: Disable parity reporting Bjorn Helgaas
2021-03-30 17:43 ` [PATCH v4 3/3] ARM: iop32x: disable N2100 PCI " Bjorn Helgaas
2021-03-31 11:08 ` Heiner Kallweit [this message]
2021-03-31 11:26 ` [PATCH v4 0/3] PCI: Disable parity checking Krzysztof Wilczyński
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=3ed9ff5a-3984-1abd-c857-dd5ca942fcde@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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).