From: Bjorn Helgaas <helgaas@kernel.org>
To: Arun Easi <aeasi@marvell.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Girish Basrur <GBasrur@marvell.com>,
Quinn Tran <qutran@marvell.com>
Subject: Re: [EXT] Re: [PATCH] PCI/VPD: Remove VPD quirk for QLogic 1077:2261
Date: Thu, 25 Feb 2021 14:42:08 -0600 [thread overview]
Message-ID: <20210225204208.GA29802@bjorn-Precision-5520> (raw)
In-Reply-To: <alpine.LRH.2.21.9999.2102251157270.13940@irv1user01.caveonetworks.com>
On Thu, Feb 25, 2021 at 12:15:33PM -0800, Arun Easi wrote:
> On Thu, 25 Feb 2021, 11:56am, Bjorn Helgaas wrote:
> > On Thu, Feb 25, 2021 at 11:32:28AM -0800, Arun Easi wrote:
> > > On Thu, 25 Feb 2021, 8:31am, Bjorn Helgaas wrote:
> > > > On Wed, Feb 24, 2021 at 03:00:18PM -0800, Arun Easi wrote:
> > > > > On Fri, 18 Dec 2020, 5:04pm, Arun Easi wrote:
> > > > >
> > > > > > The VPD quirk was added by [0] to avoid a system NMI; this issue
> > > > > > has been long fixed in the HBA firmware. In addition, PCI also has
> > > > > > the logic to check the VPD size [1], so this quirk can be reverted
> > > > > > now. More details in the thread:
> > > > > > "VPD blacklist of Marvell QLogic 1077/2261" [2].
> > > > > >
> > > > > > [0] 0d5370d1d852 ("PCI: Prevent VPD access for QLogic ISP2722")
> > > > > > [1] 104daa71b396 ("PCI: Determine actual VPD size on first access")
> > > > > > [2] https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_linux-2Dpci_alpine.LRH.2.21.9999.2012161641230.28924-40irv1user01.caveonetworks.com_&d=DwIBAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=P-q_Qkt75qFy33SvdD2nAxAyN87eO1d-mFO-lqNOomw&m=Bw8qGbVsETqSibSD8JVMAxZh8BCn1cHuskKjbarfuT8&s=IMvYnIBgaHJkzF2-GgIrGymbRguV287NVLG1_KcP_po&e=
> > > > > >
> > > > > > Signed-off-by: Arun Easi <aeasi@marvell.com>
> > > > > > CC: stable@vger.kernel.org # v4.6+
> > > > > > ---
> > > > >
> > > > > Wondering if there is something needed from my side. I could not find this
> > > > > in the v5.12 list.
> > > >
> > > > Sorry, I blew it on this one (and other VPD patches from Heiner).
> > > > It's too late for v5.12, but I'll try again for v5.13.
> > > >
> > >
> > > No worries. As these are mostly one-liners and straight forward changes,
> > > posting during RC is not an option for 5.12 inclusion?
> >
> > Not unless it's critical or it fixes a bug we introduced during the
> > merge window. This doesn't seem like either, but please clarify if it
> > is.
> >
> > From the commit log, it looks like this is just a cleanup with no
> > benefit to the user. If that's the case, there's no reason to
> > backport to stable either.
>
> Actually, this fixes the issue that block users from seeing VPD data in
> "lspci -vvv" listing. My bad in not stating that well in the commit log.
> In retrospect, this was mentioned only in a prior e-mail (link[2] above --
> sorry about our exchange servers mangling the URL and redirecting it via
> proofpoint).
>
> I can re-send the patch to correctly reflect it as a fix. Something like:
>
> Subject: "PCI/VPD: Fix blocking of VPD data in lspci for QLogic 1077:2261"
Yes, that would be useful :) The commit log needs to explain why the
patch should be merged.
Bjorn
prev parent reply other threads:[~2021-02-25 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 1:04 [PATCH] PCI/VPD: Remove VPD quirk for QLogic 1077:2261 Arun Easi
2021-02-24 23:00 ` Arun Easi
2021-02-25 16:31 ` Bjorn Helgaas
2021-02-25 19:32 ` [EXT] " Arun Easi
2021-02-25 19:56 ` Bjorn Helgaas
2021-02-25 20:15 ` Arun Easi
2021-02-25 20:42 ` 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=20210225204208.GA29802@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=GBasrur@marvell.com \
--cc=aeasi@marvell.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=qutran@marvell.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