Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 1/1] ASoC: stm32: add of dependency for stm32 drivers
Date: Thu, 1 Feb 2018 14:24:55 +0000	[thread overview]
Message-ID: <20180201142455.GB10785@sirena.org.uk> (raw)
In-Reply-To: <3bd3ba89-5c69-4485-c913-ff1c1ad67190@st.com>

On Thu, Feb 01, 2018 at 01:19:28PM +0000, Olivier MOYSAN wrote:
> On 02/01/2018 10:10 AM, Ladislav Michl wrote:

> > depends on (ARCH_STM32 && OF) || COMPILE_TEST ?

> I can find in many configs "depends on OF && (ARCH_X || COMPILE_TEST)"
> This seems reasonable to me, as the driver always requires OF 
> dependency, regardless the compilation context.
> In fact, I cannot see why OF would not have to be selected
> for COMPILE_TEST.

There are some OF functions that are stubbed out when OF is disabled and
some that aren't, if the driver is using the more obscure APIs that
aren't stubbed it needs the hard dependency but if it's using the other
bits that do have the stubs then it can be compile tested without OF
being abled.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180201/01601556/attachment-0001.sig>

      reply	other threads:[~2018-02-01 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  8:54 [PATCH 1/1] ASoC: stm32: add of dependency for stm32 drivers Olivier Moysan
2018-02-01  9:10 ` [alsa-devel] " Ladislav Michl
2018-02-01 13:19   ` Olivier MOYSAN
2018-02-01 14:24     ` Mark Brown [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=20180201142455.GB10785@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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