From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Marc Zyngier <maz@kernel.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-arm-kernel@lists.infradead.org,
"Thomas Gleixner" <tglx@linutronix.de>,
kernel-team@android.com,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH] irqchip/wpcm450: Drop COMPILE_TEST
Date: Thu, 8 Apr 2021 13:51:33 +0200 [thread overview]
Message-ID: <YG7uRcKSGAxJDSuW@latitude> (raw)
In-Reply-To: <0dd30fb16e1b9d9c7fe226cc102f8fac@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 557 bytes --]
On Thu, Apr 08, 2021 at 11:43:19AM +0100, Marc Zyngier wrote:
> On 2021-04-08 09:45, Jonathan Neuschäfer wrote:
[...]
> > I guess I could use (COMPILE_TEST && ARM) or something…
>
> One of the major interest of COMPILE_TEST to be able to check code
> cross-architecture. For code that cannot compile cross-architecture,
> I'm not sure it matters much.
>
> We can achieve the same result by enabling multi-platform builds (and
> this system should probably end-up in multi_v5_defconfig).
Alright, thanks for the explanation.
Jonathan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-04-08 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:00 [PATCH] irqchip/wpcm450: Drop COMPILE_TEST Marc Zyngier
2021-04-08 8:45 ` Jonathan Neuschäfer
2021-04-08 10:43 ` Marc Zyngier
2021-04-08 11:51 ` Jonathan Neuschäfer [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=YG7uRcKSGAxJDSuW@latitude \
--to=j.neuschaefer@gmx.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).