linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] PCI: pci-bridge-emul: Various fixes
Date: Tue, 30 Nov 2021 14:26:52 +0100	[thread overview]
Message-ID: <20211130142652.30654ce5@thinkpad> (raw)
In-Reply-To: <20211124155944.1290-1-pali@kernel.org>

On Wed, 24 Nov 2021 16:59:38 +0100
Pali Rohár <pali@kernel.org> wrote:

> This patch series contains various fixes for pci-bridge-emul code.
> This code is used only by pci-aardvark.c and pci-mvebu.c drivers.
> 
> Pali Rohár (6):
>   PCI: pci-bridge-emul: Make expansion ROM Base Address register
>     read-only
>   PCI: pci-bridge-emul: Properly mark reserved PCIe bits in PCI config
>     space
>   PCI: pci-bridge-emul: Add definitions for missing capabilities
>     registers
>   PCI: pci-bridge-emul: Fix definitions of reserved bits
>   PCI: pci-bridge-emul: Correctly set PCIe capabilities
>   PCI: pci-bridge-emul: Set PCI_STATUS_CAP_LIST for PCIe device
> 
>  drivers/pci/controller/pci-aardvark.c |   4 +-
>  drivers/pci/controller/pci-mvebu.c    |   8 ++
>  drivers/pci/pci-bridge-emul.c         | 113 ++++++++++++++++++++++----
>  3 files changed, 108 insertions(+), 17 deletions(-)
> 

I will send v2 of this series with the third patch dropped, since it
will be applied via aardvark batch 3 series.

Marek

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-11-30 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 15:59 [PATCH 0/6] PCI: pci-bridge-emul: Various fixes Pali Rohár
2021-11-24 15:59 ` [PATCH 1/6] PCI: pci-bridge-emul: Make expansion ROM Base Address register read-only Pali Rohár
2021-11-24 15:59 ` [PATCH 2/6] PCI: pci-bridge-emul: Properly mark reserved PCIe bits in PCI config space Pali Rohár
2021-11-24 15:59 ` [PATCH 3/6] PCI: pci-bridge-emul: Add definitions for missing capabilities registers Pali Rohár
2021-11-24 15:59 ` [PATCH 4/6] PCI: pci-bridge-emul: Fix definitions of reserved bits Pali Rohár
2021-11-24 15:59 ` [PATCH 5/6] PCI: pci-bridge-emul: Correctly set PCIe capabilities Pali Rohár
2021-11-24 15:59 ` [PATCH 6/6] PCI: pci-bridge-emul: Set PCI_STATUS_CAP_LIST for PCIe device Pali Rohár
2021-11-30 13:26 ` Marek Behún [this message]
2021-12-02 20:20   ` [PATCH 0/6] PCI: pci-bridge-emul: Various fixes Pali Rohár
2021-12-06 12:19 ` Lorenzo Pieralisi
2021-12-06 12:24   ` Pali Rohár
2021-12-06 14:26     ` Lorenzo Pieralisi

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=20211130142652.30654ce5@thinkpad \
    --to=kabel@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pali@kernel.org \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.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).