From: "Marek Behún" <marek.behun@nic.cz>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
linux-pci@vger.kernel.org,
Rötti <espressobinboardarmbiantempmailaddress@posteo.de>,
"Pali Rohár" <pali@kernel.org>,
stable@vger.kernel.org, "Zachary Zhang" <zhangzg@marvell.com>
Subject: Re: [PATCH] PCI: Add Max Payload Size quirk for ASMedia ASM1062 SATA controller
Date: Fri, 16 Apr 2021 15:54:00 +0200 [thread overview]
Message-ID: <20210416155400.695f7629@dellmb> (raw)
In-Reply-To: <20210317224549.GA93134@bjorn-Precision-5520>
On Wed, 17 Mar 2021 17:45:49 -0500
Bjorn Helgaas <helgaas@kernel.org> wrote:
> Can you please open a report at bugzilla.kernel.org and attach the
> complete "sudo lspci -vv" output for both systems? I think it's OK to
> collect these with the patch applied; we should still be able to see
> the information we use to compute the MPS values. But please include
> the CONFIG_PCIE_BUS_* settings and any "pcie_bus_*" kernel command
> line arguments.
Bjorn, I have submitted a report on bugzilla
https://bugzilla.kernel.org/show_bug.cgi?id=212695
is this enough?
Marek
next prev parent reply other threads:[~2021-04-16 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:59 [PATCH] PCI: Add Max Payload Size quirk for ASMedia ASM1062 SATA controller Marek Behún
2021-03-17 18:46 ` Pali Rohár
2021-03-17 22:45 ` Bjorn Helgaas
2021-03-17 22:55 ` Pali Rohár
2021-03-17 23:03 ` Bjorn Helgaas
2021-03-19 19:02 ` Pali Rohár
2021-03-21 15:09 ` Rötti
2021-05-30 10:21 ` Pali Rohár
2021-08-26 11:00 ` Rötti
2021-03-17 23:09 ` Marek Behún
2021-04-16 13:54 ` Marek Behún [this message]
2021-04-25 15:29 ` Pali Rohár
2021-05-11 16:16 ` Marek Behún
2021-05-28 0:12 ` Pali Rohár
2021-06-01 17:09 ` Bjorn Helgaas
2021-06-01 21:15 ` Bjorn Helgaas
2021-06-01 11:36 ` 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=20210416155400.695f7629@dellmb \
--to=marek.behun@nic.cz \
--cc=espressobinboardarmbiantempmailaddress@posteo.de \
--cc=helgaas@kernel.org \
--cc=kabel@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhangzg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.