From: Russell King <rmk@arm.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-arch@vger.kernel.org,
Alessandro Guido <alessandro.guido@gmail.com>,
cpufreq@lists.linux.org.uk, davej@codemonkey.org.uk
Subject: Re: [PATCH] Use menuconfig for CONFIG_CPU_FREQ
Date: Thu, 14 Feb 2008 07:51:15 +0000 [thread overview]
Message-ID: <20080214075115.GB17110@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0802140246440.1822@scrub.home>
On Thu, Feb 14, 2008 at 02:47:56AM +0100, Roman Zippel wrote:
> Hi,
>
> On Wed, 13 Feb 2008, Russell King wrote:
>
> > > No because they all depend on CPU_FREQ and as far as I understand Kconfig
> > > automagically puts them under the same menu.
> >
> > Hmm, that's not documented behaviour. If we're starting to rely on that
> > maybe it should be documented as being the expected behaviour?
>
> It is. :)
I disagree.
> Look for "Menu structure" in kconfig-language.txt.
Yes, I read that and didn't get the answer to the question above. It's
unclear how:
config CPU_FREQ_INTEGRATOR
tristate "CPUfreq driver for ARM Integrator CPUs"
depends on ARCH_INTEGRATOR && CPU_FREQ
being under CPU_FREQ rather than ARCH_INTEGRATOR
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-02-14 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 22:30 [PATCH] Use menuconfig for CONFIG_CPU_FREQ Alessandro Guido
2008-02-13 22:50 ` Russell King
2008-02-13 23:00 ` Alessandro Guido
2008-02-13 23:15 ` Russell King
2008-02-14 1:47 ` Roman Zippel
2008-02-14 7:51 ` Russell King [this message]
2008-02-14 8:44 ` [PATCH v2] " Alessandro Guido
2008-02-14 14:00 ` [PATCH] " Roman Zippel
2008-02-14 15:08 ` Russell King
2008-02-14 18:03 ` Roman Zippel
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=20080214075115.GB17110@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alessandro.guido@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=zippel@linux-m68k.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