mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Pramod Gurav <pramod.gurav@smartplayin.com>,
	Stanimir Varbanov <svarbanov@mm-sol.com>,
	pramod.gurav.etc@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	Josh Cartwright <joshc@codeaurora.org>
Subject: Re: [PATCH] regmap: Kconfig: Select SPMI when REGMAP_SPMI is selected
Date: Wed, 16 Jul 2014 15:18:42 +0100	[thread overview]
Message-ID: <20140716141842.GO17528@sirena.org.uk> (raw)
In-Reply-To: <1405519254.31919.24.camel@iivanov-dev>

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Wed, Jul 16, 2014 at 05:00:54PM +0300, Ivan T. Ivanov wrote:
> On Wed, 2014-07-16 at 14:53 +0100, Mark Brown wrote:

> > No, this isn't an either/or thing - the dependency is absolutely
> > mandatory if the device needs SPMI.  The defconfigs are a separate
> > thing, they just exist to give people a starting point for configuring
> > their kernel so if the device using SPMI is important for relevant
> > systems the defconfig needs to be set up to enable it but that's
> > separate to the dependency since there's no need for people to ever even
> > look at defconfigs.

> Then config REGMAP_SPMI should depend on SPMI, right?

No, REGMAP_SPMI is not something that can be enabled directly - it is
selected by its users which should be ensuring that SPMI is enabled as
it is difficult to see a use case for REGMAP_SPMI which does not do
this.

A dependency from a selected symbol will have no effect.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-07-16 14:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 11:39 pramod.gurav.etc
2014-07-16 12:07 ` Stanimir Varbanov
2014-07-16 12:14   ` Pramod Gurav
2014-07-16 12:25     ` Stanimir Varbanov
2014-07-16 12:56       ` Pramod Gurav
2014-07-16 13:53         ` Stanimir Varbanov
2014-07-16 13:53         ` Mark Brown
2014-07-16 14:00           ` Ivan T. Ivanov
2014-07-16 14:18             ` Mark Brown [this message]
2014-07-16 14:42               ` pramod gurav
2014-07-16 14:48                 ` Mark Brown
2014-07-16 12:19 ` Lars-Peter Clausen

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=20140716141842.GO17528@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=iivanov@mm-sol.com \
    --cc=joshc@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pramod.gurav.etc@gmail.com \
    --cc=pramod.gurav@smartplayin.com \
    --cc=svarbanov@mm-sol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®