From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Vincent Legoll <vincent.legoll@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: Make HWSPINLOCK a menuconfig to ease disabling
Date: Thu, 6 Jul 2017 23:27:01 -0400 [thread overview]
Message-ID: <20170707032701.m24ibfvqirpsxklh@codemonkey.org.uk> (raw)
In-Reply-To: <20170706232350.E40BE22E2F@pdx-korg-gitolite-1.ci.codeaurora.org>
On Thu, Jul 06, 2017 at 11:23:50PM +0000, Linux Kernel wrote:
> Make HWSPINLOCK a menuconfig to ease disabling
>
> So that there's no need to get into the submenu to disable all related config
> entries.
Here's how that looks on x86...
*
* Hardware Spinlock drivers
*
Hardware Spinlock drivers (HWSPINLOCK) [N/m/y] (NEW) ?
There is no help available for this option.
Symbol: HWSPINLOCK [=n]
Type : tristate
Prompt: Hardware Spinlock drivers
Location:
-> Device Drivers
Defined at drivers/hwspinlock/Kconfig:5
No help ? Ok whatever, let's see what happens..
Hardware Spinlock drivers (HWSPINLOCK) [N/m/y] (NEW) m
And then nothing, because none of the drivers that depend on this are available for x86
because of stuff like this..
> config HWSPINLOCK_OMAP
> tristate "OMAP Hardware Spinlock device"
> depends on ARCH_OMAP4 || SOC_OMAP5 || SOC_DRA7XX || SOC_AM33XX || SOC_AM43XX
> config HWSPINLOCK_QCOM
> tristate "Qualcomm Hardware Spinlock device"
> depends on ARCH_QCOM
> config HWSPINLOCK_SIRF
> tristate "SIRF Hardware Spinlock device"
> depends on ARCH_SIRF
> config HSEM_U8500
> tristate "STE Hardware Semaphore functionality"
> depends on ARCH_U8500
HWSPINLOCK needs all those depends too.
Dave
parent reply other threads:[~2017-07-07 3:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170706232350.E40BE22E2F@pdx-korg-gitolite-1.ci.codeaurora.org>]
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=20170707032701.m24ibfvqirpsxklh@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.legoll@gmail.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
all inboxes | Powered by JetHome®