All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Gouders <dirk@gouders.net>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 2/2] kconfig: fix comment for symbol flag SYMBOL_AUTO
Date: Tue, 03 Jul 2018 09:32:36 +0200	[thread overview]
Message-ID: <ghzhz8wz8r.fsf@lena.gouders.net> (raw)
In-Reply-To: <CAK7LNASQ6mJkn69BkLm40t8-dxJfdQJ+G0nBrtUCeU2hBN_b3Q@mail.gmail.com> (Masahiro Yamada's message of "Tue, 3 Jul 2018 00:14:52 +0900")

Masahiro Yamada <yamada.masahiro@socionext.com> writes:

> 2018-06-29 18:12 GMT+09:00 Dirk Gouders <dirk@gouders.net>:
>> I could not verify the comment for that symbol flag.
>
> Good catch.
> I forgot to fix up the comment
> in commit 104daea149c4.
>
>
>> I could only find that flag set for choices and the defconfig_list
>> symbol in a dump of all symbols, which corresponds to the only two
>> locations in the code where that flag is being set explicitely.
>>
>> Signed-off-by: Dirk Gouders <dirk@gouders.net>
>> Cc: Sam Ravnborg <sam@ravnborg.org>
>> ---
>>  scripts/kconfig/expr.h | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/scripts/kconfig/expr.h b/scripts/kconfig/expr.h
>> index 94a383b21df6..0f53e44f14d6 100644
>> --- a/scripts/kconfig/expr.h
>> +++ b/scripts/kconfig/expr.h
>> @@ -141,7 +141,9 @@ struct symbol {
>>  #define SYMBOL_OPTIONAL   0x0100  /* choice is optional - values can be 'n' */
>>  #define SYMBOL_WRITE      0x0200  /* write symbol to file (KCONFIG_CONFIG) */
>>  #define SYMBOL_CHANGED    0x0400  /* ? */
>> -#define SYMBOL_AUTO       0x1000  /* value from environment variable */
>> +#define SYMBOL_AUTO       0x1000  /* Symbols of type choice and the
>> +                                  * symbol with option defconfig_list
>> +                                  * have this flag set */
>
> Hmm.  This explanation is not very helpful in my opinion.
> Could you reword that?
>
> In my understanding, symbols with SYMBOL_AUTO
> are never written out to file.

Yes, that's right, sym_calc_value() clears SYMBOL_WRITE for those
symbols and the comment should describe the effect of the flag, not it's
users.  I will read a bit more to see if the flag has more effects and
reword the comment.

Sidenote: probably, AUTO is a misnomer for this flag.  I would expect
something like automatically generated symbols but the symbols that have
this flag set are rather -- hmm, perhaps auxiliary symbols?

Dirk

  reply	other threads:[~2018-07-03  7:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 19:27 [PATCH 0/3] Fixes concerning zconfdump() Dirk Gouders
2018-06-22 19:27 ` [PATCH 1/3] kconfig: avoid assert()-triggered segfaults in xfwrite() Dirk Gouders
2018-06-27 16:29   ` Masahiro Yamada
2018-06-27 19:23     ` Dirk Gouders
2018-06-29  9:12       ` [PATCH 0/2] kconfig: expr_print(): print constant symbols within quotes Dirk Gouders
2018-06-29  9:12         ` [PATCH v2 1/2] " Dirk Gouders
2018-06-29  9:12         ` [PATCH 2/2] kconfig: fix comment for symbol flag SYMBOL_AUTO Dirk Gouders
2018-07-02 15:14           ` Masahiro Yamada
2018-07-03  7:32             ` Dirk Gouders [this message]
2018-07-03  7:51               ` Masahiro Yamada
2018-07-03  9:37                 ` Dirk Gouders
2018-07-03 12:43                   ` [PATCH v3] kconfig: rename SYMBOL_AUTO to SYMBOL_NO_WRITE Dirk Gouders
2018-07-06  2:54                     ` Masahiro Yamada
2018-07-03  9:10             ` [PATCH v2] kconfig: fix comment for symbol flag SYMBOL_AUTO Dirk Gouders
2018-06-22 19:27 ` [PATCH 2/3] kconfig: handle P_SYMBOL in print_symbol() Dirk Gouders
2018-06-27 16:30   ` Masahiro Yamada
2018-06-22 19:27 ` [PATCH 3/3] kconfig: add debugconfig target for debugging purposes Dirk Gouders
2018-07-05  9:31   ` Masahiro Yamada
2018-07-05 11:51     ` Dirk Gouders

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=ghzhz8wz8r.fsf@lena.gouders.net \
    --to=dirk@gouders.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=yamada.masahiro@socionext.com \
    /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.