Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211001053253.1223316-1-masahiroy@kernel.org>
 <20211001053253.1223316-3-masahiroy@kernel.org> <boris.20211028071331@codesynthesis.com>
In-Reply-To: <boris.20211028071331@codesynthesis.com>
From:   Masahiro Yamada <masahiroy@kernel.org>
Date:   Fri, 5 Nov 2021 17:46:12 +0900
Message-ID: <CAK7LNASx05b8pWJDaBbRE8rMZ_ceL1qFCMZQ9Dy21pJsuTM_+w@mail.gmail.com>
Subject: Re: [PATCH 03/10] kconfig: refactor conf_write_symbol()
To:     Boris Kolpackov <boris@codesynthesis.com>
Cc:     Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Oct 28, 2021 at 2:16 PM Boris Kolpackov <boris@codesynthesis.com> wrote:
>
> Masahiro Yamada <masahiroy@kernel.org> writes:
>
> > +static void __print_symbol(FILE *fp, struct symbol *sym, enum output_n output_n,
>
> Identifier that start with double underscore are reserved. The same
> goes for __conf_write_autoconf() in another patch.


Without this patch, there are some functions that start with double underscores.

For example,

  __expr_eliminate_eq() in scripts/kconfig/expr.c
  __expand_string()  in scripts/kconfig/preprocess.c

Are they problematic as well?


-- 
Best Regards
Masahiro Yamada