From: "Marek Behún" <kabel@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: pali@kernel.org, linux-pci@vger.kernel.org,
"Marek Behún" <kabel@kernel.org>
Subject: [PATCH v3 00/11] PCI: aardvark controller fixes BATCH 3
Date: Tue, 30 Nov 2021 14:25:12 +0100 [thread overview]
Message-ID: <20211130132523.28126-1-kabel@kernel.org> (raw)
Dear Lorenzo,
sorry about this, I overlooked one more change Pali did in the second
patch.
Changes since v2:
- updated the second patch, updated definitions of registers
PCI_EXP_DEVCAP2 and PCI_EXP_DEVCTL2
Changes since v1:
- removed fixes / stable tags
- split the patches as you first suggested, since it makes more sense
IMO
- changed some commit messages a little
Marek
Pali Rohár (11):
PCI: pci-bridge-emul: Add description for class_revision field
PCI: pci-bridge-emul: Add definitions for missing capabilities
registers
PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2
registers on emulated bridge
PCI: aardvark: Clear all MSIs at setup
PCI: aardvark: Comment actions in driver remove method
PCI: aardvark: Disable bus mastering when unbinding driver
PCI: aardvark: Mask all interrupts when unbinding driver
PCI: aardvark: Fix memory leak in driver unbind
PCI: aardvark: Assert PERST# when unbinding driver
PCI: aardvark: Disable link training when unbinding driver
PCI: aardvark: Disable common PHY when unbinding driver
drivers/pci/controller/pci-aardvark.c | 65 ++++++++++++++++++++++++---
drivers/pci/pci-bridge-emul.c | 49 +++++++++++++++++++-
2 files changed, 107 insertions(+), 7 deletions(-)
--
2.32.0
next reply other threads:[~2021-11-30 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 13:25 Marek Behún [this message]
2021-11-30 13:25 ` [PATCH v3 01/11] PCI: pci-bridge-emul: Add description for class_revision field Marek Behún
2021-11-30 13:25 ` [PATCH v3 02/11] PCI: pci-bridge-emul: Add definitions for missing capabilities registers Marek Behún
2021-11-30 13:25 ` [PATCH v3 03/11] PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge Marek Behún
2021-11-30 13:25 ` [PATCH v3 04/11] PCI: aardvark: Clear all MSIs at setup Marek Behún
2021-11-30 13:25 ` [PATCH v3 05/11] PCI: aardvark: Comment actions in driver remove method Marek Behún
2021-11-30 13:25 ` [PATCH v3 06/11] PCI: aardvark: Disable bus mastering when unbinding driver Marek Behún
2021-11-30 13:25 ` [PATCH v3 07/11] PCI: aardvark: Mask all interrupts " Marek Behún
2021-11-30 13:25 ` [PATCH v3 08/11] PCI: aardvark: Fix memory leak in driver unbind Marek Behún
2021-11-30 13:25 ` [PATCH v3 09/11] PCI: aardvark: Assert PERST# when unbinding driver Marek Behún
2021-11-30 13:25 ` [PATCH v3 10/11] PCI: aardvark: Disable link training " Marek Behún
2021-11-30 13:25 ` [PATCH v3 11/11] PCI: aardvark: Disable common PHY " Marek Behún
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=20211130132523.28126-1-kabel@kernel.org \
--to=kabel@kernel.org \
--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.