From: "Marek Behún" <kabel@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: pali@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 00/13] PCI: aardvark controller fixes
Date: Thu, 7 Oct 2021 19:36:16 +0200 [thread overview]
Message-ID: <20211007193616.5adf25f6@thinkpad> (raw)
In-Reply-To: <163361366612.462.10245349222624047259.b4-ty@arm.com>
On Thu, 7 Oct 2021 14:38:25 +0100
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> On Tue, 5 Oct 2021 20:09:39 +0200, Marek Behún wrote:
> > as requested I am sending v2 of this series.
> >
> > Changes since v1:
> > - updated commit message in patch 6 as suggested by Mark
> > - updated patch 6 to also drop the early return
> > - changed the LTSSM definitions to enum in patch 12
> > - dropped the Fixes tags for those patches where it was inappropriate
> >
> > [...]
>
> I rewrote some logs, dropped some stable tags. This series raised
> a couple of interesting questions that may be relevant for PCI core
> as well, it'd be great if those won't be lost but I feel it is time
> to merge this series to help Marek/Pali cut the patch delta and
> give this code wider testing.
>
> I have applied it to pci/aardvark, please _do_ have a look and
> report back any issue with it.
I checked all the commit messages in pci/aardvark.
I also compiled this branch and tested it on my Mox with ath10k card
and it works correctly, no regressions.
Marek
prev parent reply other threads:[~2021-10-07 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 18:09 [PATCH v2 00/13] PCI: aardvark controller fixes Marek Behún
2021-10-05 18:09 ` [PATCH v2 01/13] PCI: Add PCI_EXP_DEVCTL_PAYLOAD_* macros Marek Behún
2021-10-05 18:09 ` [PATCH v2 02/13] PCI: aardvark: Fix PCIe Max Payload Size setting Marek Behún
2021-10-05 18:09 ` [PATCH v2 03/13] PCI: aardvark: Don't spam about PIO Response Status Marek Behún
2021-10-05 18:09 ` [PATCH v2 04/13] PCI: aardvark: Fix preserving PCI_EXP_RTCTL_CRSSVE flag on emulated bridge Marek Behún
2021-10-05 18:09 ` [PATCH v2 05/13] PCI: aardvark: Fix configuring Reference clock Marek Behún
2021-10-05 18:09 ` [PATCH v2 06/13] PCI: aardvark: Do not clear status bits of masked interrupts Marek Behún
2021-10-05 18:09 ` [PATCH v2 07/13] PCI: aardvark: Do not unmask unused interrupts Marek Behún
2021-10-06 9:13 ` Lorenzo Pieralisi
2021-10-06 10:28 ` Marek Behún
2021-10-07 13:27 ` Lorenzo Pieralisi
2021-10-05 18:09 ` [PATCH v2 08/13] PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() Marek Behún
2021-10-05 18:09 ` [PATCH v2 09/13] PCI: aardvark: Implement re-issuing config requests on CRS response Marek Behún
2021-10-05 18:09 ` [PATCH v2 10/13] PCI: aardvark: Simplify initialization of rootcap on virtual bridge Marek Behún
2021-10-05 18:09 ` [PATCH v2 11/13] PCI: aardvark: Fix link training Marek Behún
2021-10-07 11:55 ` Lorenzo Pieralisi
2021-10-07 12:33 ` Marek Behún
2021-10-05 18:09 ` [PATCH v2 12/13] PCI: aardvark: Fix checking for link up via LTSSM state Marek Behún
2021-10-05 18:09 ` [PATCH v2 13/13] PCI: aardvark: Fix reporting Data Link Layer Link Active Marek Behún
2021-10-07 13:38 ` [PATCH v2 00/13] PCI: aardvark controller fixes Lorenzo Pieralisi
2021-10-07 17:36 ` Marek Behún [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=20211007193616.5adf25f6@thinkpad \
--to=kabel@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@kernel.org \
/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.