From: Mark Brown <broonie@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Icenowy Zheng <icenowy@aosc.io>
Subject: Re: [PATCH] regulator: Drop obsolete dependencies on COMPILE_TEST
Date: Thu, 24 Nov 2022 16:52:23 +0000 [thread overview]
Message-ID: <Y3+hR9MYueN1FNZd@sirena.org.uk> (raw)
In-Reply-To: <20221124144708.64371b98@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Thu, Nov 24, 2022 at 02:47:08PM +0100, Jean Delvare wrote:
> It is actually better to always build such drivers with OF enabled,
> so that the test builds are closer to how each driver will actually be
> built on its intended target. Building them without OF may not test
> much as the compiler will optimize out potentially large parts of the
> code. In the worst case, this could even pop false positive warnings.
Having the ability to build without OF doesn't preclude testing with OF
of course.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-24 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 13:47 Jean Delvare
2022-11-24 16:52 ` Mark Brown [this message]
2022-11-24 18:11 ` Mark Brown
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=Y3+hR9MYueN1FNZd@sirena.org.uk \
--to=broonie@kernel.org \
--cc=icenowy@aosc.io \
--cc=jdelvare@suse.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®