From: Randy Dunlap <randy.dunlap@oracle.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Yihe Chen <yihect@juliantec.info>,
linux kbuild list <linux-kbuild@vger.kernel.org>
Subject: Re: config help
Date: Mon, 1 Nov 2010 10:46:18 -0700 [thread overview]
Message-ID: <20101101104618.319b5482.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTikTLGett2Tinn9+x6Srd5Hre9zKHLb+g8+KJCym@mail.gmail.com>
On Mon, 1 Nov 2010 13:41:33 -0400 Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Nov 1, 2010 at 12:31 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > Anyway, in 2.6.35, scripts/kconfig/Makefile is fairly clear on those
> > short option strings:
> >
> > -o oldconfig
> > -s silentoldconfig
> > -r randconfig
> > -y allyesconfig
> > -n allnoconfig
> > -m allmodconfig
> > -d defconfig
> > -D filename use filename as default configuration
> >
> This is no longer the case for 2.6.36. That part of `conf' has been
> moved to long options. It points to the toplev README for more info
> (which are not preset), but I don't think these low level options
> description belong there.
>
> I've got some patches in the area, that should not be long.
Hi,
Did you read the part that you snipped:
<quote>
What kernel version are you looking at? Something before 2.6.36 ?
I ask that because in 2.6.36 and later, the config command line tool only
uses long option strings (like --oldconfig), not short option strings
(like -o).
</quote>
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-01 18:02 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 ` config help Randy Dunlap
2010-10-30 1:24 ` Yihe Chen
2010-11-01 16:31 ` Randy Dunlap
2010-11-01 17:41 ` Arnaud Lacombe
2010-11-01 17:46 ` Randy Dunlap [this message]
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=20101101104618.319b5482.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=lacombar@gmail.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