From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Alex Dewar <alex.dewar90@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
linux-riscv@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
linux-pci@vger.kernel.org, Vidya Sagar <vidyas@nvidia.com>,
Dilip Kota <eswara.kota@linux.intel.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Andrew Murray <amurray@thegoodpenguin.co.uk>,
Thierry Reding <treding@nvidia.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Jonathan Chocron <jonnyc@amazon.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2] PCI: keystone: Enable compile-testing on !ARM
Date: Thu, 19 Nov 2020 10:47:37 +0000 [thread overview]
Message-ID: <160578283808.28676.5654476395812766238.b4-ty@arm.com> (raw)
In-Reply-To: <20200906195128.279342-1-alex.dewar90@gmail.com>
On Sun, 6 Sep 2020 20:51:27 +0100, 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.
>
> Build-tested with allyesconfig on x86, ppc, mips and riscv.
Applied to pci/keystone, thanks!
[1/1] PCI: keystone: Enable compile-testing on !ARM
https://git.kernel.org/lpieralisi/pci/c/476b70b4d1
Thanks,
Lorenzo
prev parent reply other threads:[~2020-11-19 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 18:56 [PATCH] PCI: keystone: Enable compile-testing on !ARM Alex Dewar
2020-09-06 12:19 ` Krzysztof Kozlowski
2020-09-06 19:48 ` Alex Dewar
2020-09-06 19:51 ` [PATCH v2] " Alex Dewar
2020-09-19 19:30 ` Alex Dewar
2020-09-30 18:21 ` Rob Herring
2020-10-10 9:04 ` Alex Dewar
2020-11-19 10:47 ` Lorenzo Pieralisi [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=160578283808.28676.5654476395812766238.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=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=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).