linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Alessandro Guido <alessandro.guido@gmail.com>,
	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 15:08:03 +0000	[thread overview]
Message-ID: <20080214150802.GA16789@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0802141351220.1822@scrub.home>

On Thu, Feb 14, 2008 at 03:00:12PM +0100, Roman Zippel wrote:
> Hi,
> 
> On Thu, 14 Feb 2008, Russell King wrote:
> 
> > 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
> 
> The doc says it looks at "the previous entry" and ARCH_INTEGRATOR isn't 
> exactly the previous entry.

Neither is CPU_FREQ "the previous entry".  The documentation is unclear.

> For me it was kind of obvious that kconfig wouldn't arbitrarily reorder 
> the menu entries.

It's always obvious for the person who wrote the code.  It isn't for those
who haven't.

> Only the indentation of an entry is changed not the 
> whole order. Any contributions to clarify this are more than welcome.

Well, I still don't have the necessary understanding to work out how
CPU_FREQ is preferred over ARCH_INTEGRATOR, even with your statements
that "it is the case".  So I'm not in a position to improve the
documentation except by adding a sentence to suggest people ask you
about it.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2008-02-14 15:13 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
2008-02-14  8:44           ` [PATCH v2] " Alessandro Guido
2008-02-14 14:00           ` [PATCH] " Roman Zippel
2008-02-14 15:08             ` Russell King [this message]
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=20080214150802.GA16789@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;
as well as URLs for NNTP newsgroup(s).