public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] kconfig: warn if an unknown symbol is selected
Date: Wed, 28 Jan 2015 16:26:50 +0100	[thread overview]
Message-ID: <54C8FFBA.5040000@suse.cz> (raw)
In-Reply-To: <1422438897.5666.23.camel@x220>

On 2015-01-28 10:54, Paul Bolle wrote:
> Now that we've been told Yann has disappeared, would you consider taking
> this patch into one of your trees? It would be nice to have people
> actually use it for a while.
> 
> Or should we first clean up (most of) the warnings it generates? There

It seems your fixes have been accepted in the meantime, but there is one
new:
*** Default configuration is based on 'x86_64_defconfig'
drivers/misc/cxl/Kconfig:8:warning: 'CXL_BASE' selects unknown symbol
'PPC_COPRO_BASE'

PPC_COPRO_BASE is not known on x86, but at the same time, there is no
way for CXL_BASE to be selected on x86:

config CXL_BASE
	bool
	default n
	select PPC_COPRO_BASE

config CXL
	tristate "Support for IBM Coherent Accelerators (CXL)"
	depends on PPC_POWERNV && PCI_MSI
	select CXL_BASE
	default m

Shouldn't we only warn about a select when it is triggered? An
allyesconfig would still report all bogus selects for given architecture.

Michal

  parent reply	other threads:[~2015-01-29  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 18:09 [PATCH 1/1] kconfig: warn if an unknown symbol is selected Paul Bolle
2014-11-03 11:38 ` Paul Bolle
     [not found]   ` <1422438897.5666.23.camel@x220>
2015-01-28 15:26     ` Michal Marek [this message]
2015-01-28 21:32       ` Paul Bolle
2015-01-29 12:39         ` Michal Marek

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=54C8FFBA.5040000@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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