mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [patch 1/1] kconfig: trivial cleanup
Date: Wed, 1 Jun 2005 18:11:36 +0200	[thread overview]
Message-ID: <200506011811.37456.blaisorblade@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.61.0506010149070.3728@scrub.home>

On Wednesday 01 June 2005 01:50, Roman Zippel wrote:
> Hi,
>
> On Tue, 31 May 2005, Blaisorblade wrote:
> > I can regenerate it only with bison 2.0, since that's what I have
> > installed. So if you don't want it to be regenerated, you cannot accept
> > my patch. I proposed sending two patches to avoid mixing the bison
> > changes with this patch changes, that's all.
>
> What I meant is a patch like this:
Ok, yes... akpm, can you merge it?
> Index: linux-2.6-mm/scripts/kconfig/zconf.tab.c_shipped
> ===================================================================
> --- linux-2.6-mm.orig/scripts/kconfig/zconf.tab.c_shipped	2005-03-16
> 13:47:36.000000000 +0100 +++
> linux-2.6-mm/scripts/kconfig/zconf.tab.c_shipped	2005-06-01
> 01:48:19.000000000 +0200 @@ -1531,7 +1531,7 @@ yyreduce:
>
>      {
>  	menu_add_entry(NULL);
> -	menu_add_prop(P_MENU, yyvsp[-1].string, NULL, NULL);
> +	menu_add_prompt(P_MENU, yyvsp[-1].string, NULL);
>  	printd(DEBUG_PARSE, "%s:%d:menu\n", zconf_curname(), zconf_lineno());
>  ;}
>      break;
> @@ -1586,7 +1586,7 @@ yyreduce:
>
>      {
>  	menu_add_entry(NULL);
> -	menu_add_prop(P_COMMENT, yyvsp[-1].string, NULL, NULL);
> +	menu_add_prompt(P_COMMENT, yyvsp[-1].string, NULL);
>  	printd(DEBUG_PARSE, "%s:%d:comment\n", zconf_curname(), zconf_lineno());
>  ;}
>      break;
> @@ -1640,7 +1640,7 @@ yyreduce:
>    case 86:
>
>      {
> -	menu_add_prop(P_PROMPT, yyvsp[-1].string, NULL, yyvsp[0].expr);
> +	menu_add_prompt(P_PROMPT, yyvsp[-1].string, yyvsp[0].expr);
>  ;}
>      break;
>
> @@ -1925,7 +1925,7 @@ void conf_parse(const char *name)
>  	sym_init();
>  	menu_init();
>  	modules_sym = sym_lookup("MODULES", 0);
> -	rootmenu.prompt = menu_add_prop(P_MENU, "Linux Kernel Configuration",
> NULL, NULL); +	rootmenu.prompt = menu_add_prompt(P_MENU, "Linux Kernel
> Configuration", NULL);
>
>  	//zconfdebug = 1;
>  	zconfparse();
>
> bye, Roman

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

  reply	other threads:[~2005-06-01 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-29 17:45 blaisorblade
2005-05-31  9:27 ` Roman Zippel
2005-05-31 20:35   ` Blaisorblade
2005-05-31 23:50     ` Roman Zippel
2005-06-01 16:11       ` Blaisorblade [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22 16:36 blaisorblade
2005-03-22 19:27 ` 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=200506011811.37456.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=akpm@osdl.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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: 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

all inboxes | Powered by JetHome®