From: Mark Brown <broonie@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chenglin Xu <chenglin.xu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>
Subject: Re: [PATCH RFC] regulator: mt6380: Fix unused array warning
Date: Wed, 27 Jul 2022 13:24:35 +0100 [thread overview]
Message-ID: <YuEug/OV9H0DKnmZ@sirena.org.uk> (raw)
In-Reply-To: <20220727140809.0951b72d@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Wed, Jul 27, 2022 at 02:08:09PM +0200, Jean Delvare wrote:
> On Wed, 27 Jul 2022 13:01:29 +0100, Mark Brown wrote:
> > It's helpful to keep the build coverage high.
> OF does not depend on the architecture, anyone can enable it. So I
> can't see any problem of coverage with making drivers depend on OF.
It still reduces a barrier to entry. It's also that it's easier to just
prefer the conditional compilation pattern rather than either check to
see which cases is needed or have people copy an example that doesn't
use it when they should.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-27 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 11:26 [PATCH RFC] regulator: mt6380: Fix unused array warning Jean Delvare
2022-07-27 12:01 ` Mark Brown
2022-07-27 12:08 ` Jean Delvare
2022-07-27 12:24 ` Mark Brown [this message]
2022-07-27 18:50 ` Jean Delvare
2022-07-27 20:10 ` Mark Brown
2022-07-28 11:15 ` AngeloGioacchino Del Regno
2022-07-29 13:23 ` Jean Delvare
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=YuEug/OV9H0DKnmZ@sirena.org.uk \
--to=broonie@kernel.org \
--cc=chenglin.xu@mediatek.com \
--cc=jdelvare@suse.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.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