LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org> To: Roman Zippel <zippel@linux-m68k.org> Cc: LKML <linux-kernel@vger.kernel.org>, linux-kbuild <linux-kbuild@vger.kernel.org> Subject: Re: kconfig: support option env="" [Was: kconfig: use $K64BIT to set 64BIT with all*config targets] Date: Mon, 14 Jan 2008 06:58:48 +0100 [thread overview] Message-ID: <20080114055848.GA5187@uranus.ravnborg.org> (raw) In-Reply-To: <Pine.LNX.4.64.0801140442420.17507@scrub.home> On Mon, Jan 14, 2008 at 04:49:48AM +0100, Roman Zippel wrote: > Hi, > > On Sun, 6 Jan 2008, Sam Ravnborg wrote: > > > Please get back to me so we can finsih this patch and have it applied. > > I will split the patch in two btw. > > I reworked the patch a little and split it into three. Thanks Roman. I will test and apply tonight. Removal of KERNELVERSION in patch #3 is wrong as the frontend uses KERNELVERSION to display the kernel version in their title. I will drop the deletion before I apply the patch. > > > > + if (sym->flags & SYMBOL_AUTO) > > > + sym->flags &= ~SYMBOL_WRITE; > > > + > > > > Why is this change needed? > > It is non-obvious to me so please explain and I will add a comment. > > Automatically generated symbols are not saved, this was previously not > needed as they weren't in the menu structure. OK > > > I did it like this: > > menu_warn(current_entry, > > "config %s: redefining environment symbol from '%s' to '%s'", > > sym->name, env, sym2->name); > > I omitted the prefix, it's inconsistent with other warnings. OK Thanks, Sam
next prev parent reply other threads:[~2008-01-14 5:58 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-10 20:40 [PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86 Sam Ravnborg 2007-11-10 20:43 ` [PATCH] kconfig: factor out code in confdata.c Sam Ravnborg 2007-11-10 20:43 ` [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets Sam Ravnborg 2007-11-10 20:43 ` [PATCH] x86: Use CONFIG_64BIT to select between 32 and 64 bit in Kconfig Sam Ravnborg 2007-11-10 20:43 ` [PATCH] kconfig: document make K64BIT=y in README Sam Ravnborg 2007-11-10 20:43 ` [PATCH] x86: introduce ARCH=i386,ARCH=x86_64 to select 32/64 bit Sam Ravnborg 2007-11-10 22:23 ` [PATCH] kconfig: document make K64BIT=y in README Randy Dunlap 2007-11-10 22:18 ` [PATCH] x86: Use CONFIG_64BIT to select between 32 and 64 bit in Kconfig Randy Dunlap 2007-11-10 20:55 ` [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets Guillaume Chazarain 2007-11-11 5:14 ` Adrian Bunk 2007-11-11 12:43 ` Guillaume Chazarain 2007-11-11 13:07 ` Adrian Bunk 2007-11-11 14:59 ` Guillaume Chazarain 2007-11-11 15:30 ` Sam Ravnborg 2007-11-11 15:55 ` Guillaume Chazarain 2007-11-10 22:16 ` Randy Dunlap 2007-11-10 22:31 ` Sam Ravnborg 2007-11-14 20:57 ` Roman Zippel 2007-11-14 22:08 ` Sam Ravnborg 2007-11-15 15:43 ` Roman Zippel 2007-11-15 19:25 ` Sam Ravnborg 2007-11-15 19:43 ` Roman Zippel 2007-11-15 20:45 ` Sam Ravnborg 2007-11-15 21:24 ` Roman Zippel 2007-11-15 22:06 ` Sam Ravnborg 2007-11-16 1:28 ` Roman Zippel 2007-11-16 3:44 ` Randy Dunlap 2007-11-16 13:02 ` Roman Zippel 2007-11-16 5:41 ` Sam Ravnborg 2007-11-16 12:54 ` Roman Zippel 2008-01-06 13:26 ` kconfig: support option env="" [Was: kconfig: use $K64BIT to set 64BIT with all*config targets] Sam Ravnborg 2008-01-14 3:49 ` Roman Zippel 2008-01-14 5:58 ` Sam Ravnborg [this message] 2008-01-14 3:50 ` [PATCH 1/3] explicitly introduce expression list Roman Zippel 2008-01-14 3:50 ` [PATCH 2/3] environment symbol support Roman Zippel 2008-01-14 3:51 ` [PATCH 3/3] use environment option Roman Zippel 2007-11-10 22:33 ` [PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86 Randy Dunlap 2007-11-10 22:50 ` Sam Ravnborg 2007-11-11 5:09 ` Adrian Bunk 2007-11-11 11:54 ` Sam Ravnborg 2007-11-12 2:47 ` Roman Zippel 2007-11-12 5:23 ` 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=20080114055848.GA5187@uranus.ravnborg.org \ --to=sam@ravnborg.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@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: linkBe 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).