From: Masahiro Yamada <masahiroy@kernel.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Ying Sun <sunying@nj.iscas.ac.cn>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Siyuan Guo <zy21df106@buaa.edu.cn>,
Randy Dunlap <rdunlap@infradead.org>,
Jesse T <mr.bossman075@gmail.com>
Subject: Re: [PATCH] kconfig: add dependency warning print about invalid values in verbose mode
Date: Thu, 24 Aug 2023 06:52:51 +0900 [thread overview]
Message-ID: <CAK7LNAQNk2MU=M5Q6GXtm34VyFcNOhVgw3UQ7Mdn4hoqQ_636A@mail.gmail.com> (raw)
In-Reply-To: <20230823015551.GB3913@google.com>
On Wed, Aug 23, 2023 at 10:56 AM Sergey Senozhatsky
<senozhatsky@chromium.org> wrote:
>
> On (23/08/19 22:40), Jesse T wrote:
> > > > From: Ying Sun <sunying@nj.iscas.ac.cn>
> > > >
> > > > Add warning about the configuration option's invalid value in verbose mode,
> > > > including error causes, mismatch dependency, old and new values,
> > > > to help users correct them.
>
> Are those really errors?
>
> ERROR : CLANG_VERSION[140006 => 0] value is invalid due to it has default value
> ERROR : CC_IS_GCC[n => y] value is invalid due to it has default value
> ERROR : GCC_VERSION[0 => 120200] value is invalid due to it has default value
>
> I'm using clang, so corresponding options are set accordingly in my .config
I think not errors, but warnings.
His idea is, CONFIG options that change a value
should be warned.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2023-08-23 21:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:24 [PATCH] kconfig: add dependency warning print about invalid values in verbose mode sunying
2023-08-19 23:01 ` Masahiro Yamada
2023-08-20 2:40 ` Jesse T
2023-08-23 1:55 ` Sergey Senozhatsky
2023-08-23 21:52 ` Masahiro Yamada [this message]
2023-08-24 0:47 ` Sergey Senozhatsky
2023-08-29 7:49 ` 郭思远
2023-09-05 9:43 ` [PATCHv2 -next] " sunying
2023-11-02 2:50 ` 郭思远
2023-11-06 3:51 ` Masahiro Yamada
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='CAK7LNAQNk2MU=M5Q6GXtm34VyFcNOhVgw3UQ7Mdn4hoqQ_636A@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.bossman075@gmail.com \
--cc=rdunlap@infradead.org \
--cc=senozhatsky@chromium.org \
--cc=sunying@nj.iscas.ac.cn \
--cc=zy21df106@buaa.edu.cn \
/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.