From: Alex Dewar <alex.dewar90@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Alex Dewar <alex.dewar90@gmail.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Thierry Reding <treding@nvidia.com>,
Andrew Murray <amurray@thegoodpenguin.co.uk>,
Vidya Sagar <vidyas@nvidia.com>,
Dilip Kota <eswara.kota@linux.intel.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Jonathan Chocron <jonnyc@amazon.com>,
linux-pci@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: keystone: Enable compile-testing on !ARM
Date: Sun, 6 Sep 2020 20:48:50 +0100 [thread overview]
Message-ID: <20200906194850.63glbnehjcuw356k@lenovo-laptop> (raw)
In-Reply-To: <CAJKOXPdjev5gMFBX8q6Q7ZZ1s3aBiGKOqfmrCQKTMGeXDeAoTA@mail.gmail.com>
On Sun, Sep 06, 2020 at 02:19:44PM +0200, Krzysztof Kozlowski wrote:
> On Fri, 4 Sep 2020 at 20:56, Alex Dewar <alex.dewar90@gmail.com> 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 on x86 with allyesconfig.
>
> You should at least build it on x86_64, powerpc and MIPS. These are
> widely available (e.g. in most of distros, or here:
> https://mirrors.edge.kernel.org/pub/tools/crosstool/). Useful is also
> riscv and sh (specially sh lacks certain headers/features).
Good suggestion. I've built it on x86, ppc, mips and riscv. sh wouldn't
build because of some kbuild dependency, rather than a compiler error.
I'll send a v2 with an updated commit message.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2020-09-06 19:49 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 [this message]
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
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=20200906194850.63glbnehjcuw356k@lenovo-laptop \
--to=alex.dewar90@gmail.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=eswara.kota@linux.intel.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=jonnyc@amazon.com \
--cc=krzk@kernel.org \
--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=m-karicheri2@ti.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).