All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Michal Marek <mmarek@suse.com>,
	Arnaud Lacombe <lacombar@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: Sync zconf.y with zconf.tab.c_shipped
Date: Tue, 12 Dec 2017 23:58:16 +0900	[thread overview]
Message-ID: <CAK7LNAT2_Su7=ADrVUsZ0EgTsyh_3QT=nWZV9E5DyFHFDhegbQ@mail.gmail.com> (raw)
In-Reply-To: <1507172808-12246-1-git-send-email-ulfalizer@gmail.com>

2017-10-05 12:06 GMT+09:00 Ulf Magnusson <ulfalizer@gmail.com>:
> Looks like a change to a comment in zconf.y was never committed, because
> the updated version only appears it zconf.tab.c_shipped. Update the
> comment in zconf.y to match.
>
> Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
> ---
>  scripts/kconfig/zconf.y | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/kconfig/zconf.y b/scripts/kconfig/zconf.y
> index c8f396c..4b2cf41 100644
> --- a/scripts/kconfig/zconf.y
> +++ b/scripts/kconfig/zconf.y
> @@ -101,7 +101,7 @@ static struct menu *current_menu, *current_entry;
>  } if_entry menu_entry choice_entry
>
>  %{
> -/* Include zconf_id.c here so it can see the token constants. */
> +/* Include kconf_id.c here so it can see the token constants. */
>  #include "kconf_id.c"
>  %}


Applied to linux-kbuild/kconfig.
Thanks!

BTW, I do not know the historical reason
why zconf instead of kconf in the first place...


-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2017-12-12 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  3:06 [PATCH] kconfig: Sync zconf.y with zconf.tab.c_shipped Ulf Magnusson
2017-12-12 14:58 ` Masahiro Yamada [this message]
2018-01-12 11:23   ` Ulf Magnusson
2018-01-12 19:38     ` Sam Ravnborg
2018-01-13  9:32       ` Ulf Magnusson

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='CAK7LNAT2_Su7=ADrVUsZ0EgTsyh_3QT=nWZV9E5DyFHFDhegbQ@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=ulfalizer@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.