From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kconfig - hex are considered decimal
Date: Tue, 1 Jul 2008 08:12:41 +0200 [thread overview]
Message-ID: <20080701061241.GA4922@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806302356340.6791@localhost.localdomain>
On Mon, Jun 30, 2008 at 11:59:42PM +0200, Roman Zippel wrote:
> Hi,
>
> On Mon, 30 Jun 2008, Sam Ravnborg wrote:
>
> > For now I added this patch (for previous mail).
> > This makes the configs equal so they can be compared.
>
> Did you try changing and saving that hex value?
Yes.
- When changing I see the 0x prefix - which I consider OK for hex values
- When saving I see the 0x prefix in autoconf.h + .config
> You need a similiar logic as used for saving the header file.
> Why is it a problem, that needs immediate fixing anyway?
To keep difference minimal for .config produced by
old style 'all*config' and new style 'all*config'.
See patches where kconfig start to use the new
method for 'all*config' targets - they are cc:ed to you
and available on linux-kbuild.
I simply started to use conf_set_all_new_symbols() and
as a result I could simplify conf.c.
And things got so simple that I dropped the patches
introducing aconf.c.
Yet TODO:
-> Give Redhat's nonint_oldconfig a closer look and see
how to integrate this functionality
-> Give Andres Salomon patches a second look and see how to
integrate the functionality he requires
It it does not turn out to be simple I will lilely postpone it
until I have moved.
Sam
next prev parent reply other threads:[~2008-07-01 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 11:51 kconfig - hex are considered decimal Sam Ravnborg
2008-06-29 21:29 ` Sam Ravnborg
2008-06-30 13:19 ` Roman Zippel
2008-06-30 20:40 ` Sam Ravnborg
2008-06-30 21:59 ` Roman Zippel
2008-07-01 6:12 ` Sam Ravnborg [this message]
2008-07-02 12:39 ` Roman Zippel
2008-07-06 21:28 ` Sam Ravnborg
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=20080701061241.GA4922@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@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