From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: Why do we need reset_control_get_optional() ?
Date: Wed, 24 Aug 2016 15:29:42 +0200 [thread overview]
Message-ID: <1472045382.5335.45.camel@pengutronix.de> (raw)
In-Reply-To: <CAK7LNARCJ0HoyUj-urFxvn2BJMjs5M1YxxEjUCRPWB9XwvvRdA@mail.gmail.com>
Am Dienstag, den 16.08.2016, 18:41 +0900 schrieb Masahiro Yamada:
> Hi Arnd,
>
> 2016-08-06 0:35 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
>
> >
> > config RESET_FOO
> > bool "FOO reset controller" if COMPILE_TEST && !ARCH_FOO
> > default ARCH_FOO
> >
> > then I think we get both: you won't be able to turn it off
> > but also get the build testing.
>
> This looks good to me, too.
> I do not know if we need "&& !ARCH_FOO", though.
>
> When we are compile-testing, we do not care if it works on run-time,
> so perhaps it makes sense to allow to enable/disable RESET_FOO
> regardless ARCH_FOO.
I'll send a few patches to add the Kconfig symbols. Turning around the
RESET_CONTROLLER selection can be done in a second step.
regards
Philipp
prev parent reply other threads:[~2016-08-24 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 11:22 Why do we need reset_control_get_optional() ? Masahiro Yamada
2016-07-28 9:43 ` Philipp Zabel
2016-07-28 10:09 ` Arnd Bergmann
2016-07-28 10:52 ` Masahiro Yamada
2016-07-28 11:00 ` Philipp Zabel
2016-08-05 15:50 ` Arnd Bergmann
2016-08-08 16:39 ` Philipp Zabel
2016-08-08 21:39 ` Arnd Bergmann
2016-08-16 14:36 ` Masahiro Yamada
2016-08-24 6:58 ` Masahiro Yamada
2016-08-24 12:30 ` Philipp Zabel
2016-07-28 10:56 ` Philipp Zabel
2016-07-28 10:29 ` Masahiro Yamada
2016-07-29 13:08 ` Philipp Zabel
2016-07-30 20:13 ` Arnd Bergmann
2016-08-05 8:55 ` Philipp Zabel
2016-08-05 15:35 ` Arnd Bergmann
2016-08-08 17:29 ` Philipp Zabel
2016-08-16 9:41 ` Masahiro Yamada
2016-08-24 13:29 ` Philipp Zabel [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=1472045382.5335.45.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).