From: Randy Dunlap <randy.dunlap@oracle.com>
To: Yihe Chen <yihect@juliantec.info>
Cc: linux kbuild list <linux-kbuild@vger.kernel.org>
Subject: Re: config help
Date: Fri, 29 Oct 2010 10:07:07 -0700 [thread overview]
Message-ID: <20101029100707.2a9afc5c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <3B997B64E0C94A689C4C5FDBD09AF912@PC200810081817>
On Fri, 29 Oct 2010 20:01:55 +0800 Yihe Chen wrote:
> Where to find information or helping stuff or usage info on those config
> tools, like conf/gconf etc.
Begin with the README file in the top-level directory of the linux source tree.
For menuconfig: use ?
For nconfig (in recent kernels): use 1 or <F1>
For gconfig: click on Help
For xconfig: click on Help
There is also some help info in Documentation/kbuild/kconfig.txt .
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-29 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:01 Yihe Chen
2010-10-29 17:07 ` Randy Dunlap [this message]
2010-10-30 1:24 ` config help Yihe Chen
2010-11-01 16:31 ` Randy Dunlap
2010-11-01 17:41 ` Arnaud Lacombe
2010-11-01 17:46 ` Randy Dunlap
2010-11-01 18:08 ` Arnaud Lacombe
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=20101029100707.2a9afc5c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=yihect@juliantec.info \
/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