From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Jörg Wedekind" <joerg@wedekind.de>,
linux-pci@vger.kernel.org, aradford@gmail.com, linux@3ware.com
Subject: Re: [PATCH] drivers/pci: disable extension-tags on 3w-9xxx controller
Date: Fri, 16 Feb 2024 12:03:12 -0600 [thread overview]
Message-ID: <20240216180312.GA1346616@bhelgaas> (raw)
In-Reply-To: <a22210a6-f9ea-d495-907d-1729dabc17fd@linux.intel.com>
On Fri, Feb 16, 2024 at 04:59:57PM +0200, Ilpo Järvinen wrote:
> On Fri, 16 Feb 2024, Jörg Wedekind wrote:
> You need to provide a description here too, the shortlog in subject is not
> enough.
Yes, we would like a little background, e.g., a URL for a bug report
if it exists, a description of how a user might recognize this
problem, etc. See https://git.kernel.org/linus/1b30dfd376e2 ("PCI:
Mark Broadcom HT1100 and HT2000 Root Port Extended Tags as broken")
for a sample.
Also update the subject line to use the same pattern as 1b30dfd376e2.
> > Signed-off-by: Jörg Wedekind <joerg@wedekind.de>
> > ---
> > drivers/pci/quirks.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> > index d797df6e5f3e..2ebbe51a7efe 100644
> > --- a/drivers/pci/quirks.c
> > +++ b/drivers/pci/quirks.c
> > @@ -5527,6 +5527,7 @@ static void quirk_no_ext_tags(struct pci_dev *pdev)
> >
> > pci_walk_bus(bridge->bus, pci_configure_extended_tags, NULL);
> > }
> > +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_3WARE, 0x1004, quirk_no_ext_tags);
> > DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0132, quirk_no_ext_tags);
> > DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0140, quirk_no_ext_tags);
> > DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0141, quirk_no_ext_tags);
> >
prev parent reply other threads:[~2024-02-16 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 10:51 [PATCH] drivers/pci: disable extension-tags on 3w-9xxx controller Jörg Wedekind
2024-02-16 14:59 ` Ilpo Järvinen
2024-02-16 18:03 ` 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=20240216180312.GA1346616@bhelgaas \
--to=helgaas@kernel.org \
--cc=aradford@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=joerg@wedekind.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux@3ware.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).