From: Alessandro Guido <alessandro.guido@gmail.com>
To: davej@codemonkey.org.uk, cpufreq@lists.linux.org.uk,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Use menuconfig for CONFIG_CPU_FREQ
Date: Thu, 14 Feb 2008 00:00:52 +0100 [thread overview]
Message-ID: <200802140000.52936.alessandro.guido@gmail.com> (raw)
In-Reply-To: <20080213225058.GA20358@flint.arm.linux.org.uk>
> Doesn't this cause these CPUFREQ options to appear outside of the CPUFREQ
> menu?
>
No because they all depend on CPU_FREQ and as far as I understand Kconfig
automagically puts them under the same menu.
next prev parent reply other threads:[~2008-02-13 23:00 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 [this message]
2008-02-13 23:15 ` Russell King
2008-02-14 1:47 ` Roman Zippel
2008-02-14 7:51 ` Russell King
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=200802140000.52936.alessandro.guido@gmail.com \
--to=alessandro.guido@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-arch@vger.kernel.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