LKML Archive on
 help / color / Atom feed
From: Georgi Djakov <>
To: Viresh Kumar <>,
	Greg Kroah-Hartman <>
Cc: Bjorn Andersson <>,
	Linux PM list <>,
	"" <>
Subject: Re: [GIT PULL] interconnect changes for 5.5
Date: Thu, 14 Nov 2019 14:59:47 +0200
Message-ID: <> (raw)
In-Reply-To: <20191114084122.35myncenejt54hht@vireshk-i7>

On 11/14/19 10:41, Viresh Kumar wrote:
> On 10-11-19, 11:16, Greg Kroah-Hartman wrote:
>> On Sat, Nov 09, 2019 at 12:27:29PM -0800, Bjorn Andersson wrote:
>>> As your question shows, everyone gets this wrong and the build breaks
>>> all the time (it's not "depends on framework", it's "depends on
>>> framework || framework=n" - and everyone you'll talk to will be
>>> puzzled as to why this is).
>> Ah, now I get it.  Yeah, that sucks.  We need a "shortcut" in Kconfig to
>> express that type of dependancy.
> Maybe we can use
> depends on framework != m

That won't work in the case where framework=m, provider=m and consumer=m.
Today this is supported by having each consumer to:
	depends on framework || !framework

So again, the problem is that we need to add something to Kconfig, even a
"shortcut", in order to express this dependency. If we convert the framework
from tristate to bool, there will be no need to touch Kconfig, as we have the
include stubs. Keeping the modular support comes at the cost of adding a
dependency to Kconfig for each user.


      reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 12:46 Georgi Djakov
2019-11-07 14:21 ` Greg Kroah-Hartman
2019-11-07 15:42   ` Georgi Djakov
2019-11-08 10:39     ` Greg Kroah-Hartman
2019-11-08 11:44       ` Georgi Djakov
2019-11-09  1:36       ` Bjorn Andersson
2019-11-09  8:48         ` Greg Kroah-Hartman
2019-11-09 20:27           ` Bjorn Andersson
2019-11-10 10:16             ` Greg Kroah-Hartman
2019-11-11  4:54               ` Viresh Kumar
2019-11-11  5:26                 ` Greg Kroah-Hartman
2019-11-14  8:41               ` Viresh Kumar
2019-11-14 12:59                 ` Georgi Djakov [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git
	git clone --mirror lkml/git/8.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone