From: Alexander Aring <aar@pengutronix.de>
To: h.morris@cascoda.com
Cc: Stefan Schmidt <stefan@osg.samsung.com>,
Marcel Holtmann <marcel@holtmann.org>,
Harry Morris <harrymorris12@gmail.com>,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH v8 0/3] ieee802154: Add support for Cascoda CA8210
Date: Fri, 17 Mar 2017 13:52:44 +0100 [thread overview]
Message-ID: <1f46560a-f28e-3121-c1e9-1bf75061cade@pengutronix.de> (raw)
In-Reply-To: <d7aa153b-3bd4-4052-65c4-c3585e970691@cascoda.com>
Hi,
On 03/02/2017 06:42 PM, Harry Morris wrote:
...
>
> I was looking into this "select vs depends on" and it seems select is by far the more widely used approach when it comes to COMMON_CLK. I guess this doesn't exactly justify it but also I agree having to manually enable it feels a bit unintuitive. I'd appreciate any further thoughts though.
>
Please note, so far I know:
Select is used mostly on Top Level Entries. It can't solve dependencies...
it can solve it, but then you need also select them in your entry.
Depends on can solve it by make it simple available only if the depended
menu entry is selected.
- Alex
next prev parent reply other threads:[~2017-03-17 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:08 [PATCH v8 0/3] ieee802154: Add support for Cascoda CA8210 Harry Morris
2017-02-06 17:08 ` [PATCH v8 1/3] ieee802154: Add CA8210 IEEE 802.15.4 device driver Harry Morris
2017-02-27 14:20 ` Stefan Schmidt
2017-02-06 17:08 ` [PATCH v8 2/3] ieee802154: Add device tree documentation for CA8210 Harry Morris
2017-02-06 17:08 ` [PATCH v8 3/3] ieee802154: Add entry in MAINTAINTERS for CA8210 driver Harry Morris
2017-02-16 16:50 ` [PATCH v8 0/3] ieee802154: Add support for Cascoda CA8210 Marcel Holtmann
2017-02-16 17:18 ` Harry Morris
2017-02-27 14:15 ` Stefan Schmidt
2017-03-02 15:08 ` Marcel Holtmann
2017-03-02 15:24 ` Stefan Schmidt
2017-03-02 17:42 ` Harry Morris
2017-03-07 19:04 ` Stefan Schmidt
2017-03-17 12:52 ` Alexander Aring [this message]
2017-03-27 14:46 ` Marcel Holtmann
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=1f46560a-f28e-3121-c1e9-1bf75061cade@pengutronix.de \
--to=aar@pengutronix.de \
--cc=h.morris@cascoda.com \
--cc=harrymorris12@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stefan@osg.samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.