public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Ying Sun <sunying@nj.iscas.ac.cn>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	sunying@nj.iscas.ac.cn, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, Siyuan Guo <zy21df106@buaa.edu.cn>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	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: Wed, 23 Aug 2023 10:55:51 +0900	[thread overview]
Message-ID: <20230823015551.GB3913@google.com> (raw)
In-Reply-To: <CAJFTR8SajdzT2kKscEpPon9faUa8tHrvYPC_+awG3VeHVS8sSg@mail.gmail.com>

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

  reply	other threads:[~2023-08-23  1:56 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 [this message]
2023-08-23 21:52       ` Masahiro Yamada
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=20230823015551.GB3913@google.com \
    --to=senozhatsky@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mr.bossman075@gmail.com \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox