From: Alex Dewar <alex.dewar90@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Dilip Kota <eswara.kota@linux.intel.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Jonathan Chocron <jonnyc@amazon.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Vidya Sagar <vidyas@nvidia.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-riscv@lists.infradead.org,
Thierry Reding <treding@nvidia.com>,
Andrew Murray <amurray@thegoodpenguin.co.uk>
Subject: Re: [PATCH v2] PCI: keystone: Enable compile-testing on !ARM
Date: Sat, 19 Sep 2020 20:30:43 +0100 [thread overview]
Message-ID: <7f78ef86-f2c5-258f-88b3-0cd79c0799ea@gmail.com> (raw)
In-Reply-To: <20200906195128.279342-1-alex.dewar90@gmail.com>
On 2020-09-06 20:51, Alex Dewar wrote:
> Currently the Keystone driver can only be compile-tested on ARM, but
> this restriction seems unnecessary. Get rid of it to increase test
> coverage.
Friendly ping?
>
> Build-tested with allyesconfig on x86, ppc, mips and riscv.
>
> Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>
> ---
> drivers/pci/controller/dwc/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
> index 044a3761c44f..ca36691314ed 100644
> --- a/drivers/pci/controller/dwc/Kconfig
> +++ b/drivers/pci/controller/dwc/Kconfig
> @@ -107,7 +107,7 @@ config PCI_KEYSTONE
>
> config PCI_KEYSTONE_HOST
> bool "PCI Keystone Host Mode"
> - depends on ARCH_KEYSTONE || ARCH_K3 || ((ARM || ARM64) && COMPILE_TEST)
> + depends on ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST
> depends on PCI_MSI_IRQ_DOMAIN
> select PCIE_DW_HOST
> select PCI_KEYSTONE
> @@ -119,7 +119,7 @@ config PCI_KEYSTONE_HOST
>
> config PCI_KEYSTONE_EP
> bool "PCI Keystone Endpoint Mode"
> - depends on ARCH_KEYSTONE || ARCH_K3 || ((ARM || ARM64) && COMPILE_TEST)
> + depends on ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST
> depends on PCI_ENDPOINT
> select PCIE_DW_EP
> select PCI_KEYSTONE
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-09-19 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200906194850.63glbnehjcuw356k@lenovo-laptop>
2020-09-06 19:51 ` [PATCH v2] PCI: keystone: Enable compile-testing on !ARM Alex Dewar
2020-09-19 19:30 ` Alex Dewar [this message]
2020-09-30 18:21 ` Rob Herring
2020-10-10 9:04 ` Alex Dewar
2020-11-19 10:47 ` 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=7f78ef86-f2c5-258f-88b3-0cd79c0799ea@gmail.com \
--to=alex.dewar90@gmail.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=aou@eecs.berkeley.edu \
--cc=bhelgaas@google.com \
--cc=eswara.kota@linux.intel.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=jonnyc@amazon.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.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).