All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-usb <linux-usb@vger.kernel.org>,
	linux-main <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Felipe Balbi" <balbi@ti.com>, "Greg KH" <greg@kroah.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	"Liam Girdwood" <lrg@slimlogic.co.uk>,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	"Hao Wu" <hao.wu@intel.com>, "Alan Cox" <alan@linux.intel.com>,
	"Mike Rapoport" <mike@compulab.co.il>
Subject: Re: [PATCH v3 2/2] drivers: cleanup Kconfig stuff
Date: Tue, 2 Nov 2010 10:39:50 -0400	[thread overview]
Message-ID: <20101102143949.GH21476@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikwGBij05h1GgW0dpvcJedmcOQ1HWCaxaBdhZta@mail.gmail.com>

On Tue, Nov 02, 2010 at 04:18:18PM +0200, Felipe Contreras wrote:
> 2010/11/2 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:

> > Well, all platforms that have TWL4030_CORE will get REGULATOR_TWL4030 by
> > default, too.  (TWL4030_CORE doesn't depend on something omapish.)

> Yes, I think TWL4030_CORE should depend on OMAP3, but I think some
> people might not like that. That's why I wanted to make that a
> separate patch.

It did originally but that dependency was removed to allow build
coverage for non-OMAP users.

> 
> > For me this looks OK.  It would be still better if it removed
> > CONFIG_REGULATOR_TWL4030=y from arch/arm/configs/omap2plus_defconfig.
> 
> Yes, but I want to run 'make savedefconfig'; there's many changes
> lingering like that.
> 
> -- 
> Felipe Contreras

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-usb <linux-usb@vger.kernel.org>,
	linux-main <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Felipe Balbi" <balbi@ti.com>, "Greg KH" <greg@kroah.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	"Liam Girdwood" <lrg@slimlogic.co.uk>,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	"Hao Wu" <hao.wu@intel.com>, "Alan Cox" <alan@linux.intel.com>,
	"Mike Rapoport" <mike@compulab.co.il>
Subject: Re: [PATCH v3 2/2] drivers: cleanup Kconfig stuff
Date: Tue, 2 Nov 2010 10:39:50 -0400	[thread overview]
Message-ID: <20101102143949.GH21476@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikwGBij05h1GgW0dpvcJedmcOQ1HWCaxaBdhZta@mail.gmail.com>

On Tue, Nov 02, 2010 at 04:18:18PM +0200, Felipe Contreras wrote:
> 2010/11/2 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:

> > Well, all platforms that have TWL4030_CORE will get REGULATOR_TWL4030 by
> > default, too.  (TWL4030_CORE doesn't depend on something omapish.)

> Yes, I think TWL4030_CORE should depend on OMAP3, but I think some
> people might not like that. That's why I wanted to make that a
> separate patch.

It did originally but that dependency was removed to allow build
coverage for non-OMAP users.

> 
> > For me this looks OK.  It would be still better if it removed
> > CONFIG_REGULATOR_TWL4030=y from arch/arm/configs/omap2plus_defconfig.
> 
> Yes, but I want to run 'make savedefconfig'; there's many changes
> lingering like that.
> 
> -- 
> Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-02 14:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02  0:14 [PATCH v3 0/2] usb: generic Kconfig fixes Felipe Contreras
2010-11-02  0:14 ` Felipe Contreras
2010-11-02  0:14 ` [PATCH v3 1/2] usb: trivial Kconfig cleanups Felipe Contreras
2010-11-02  0:14   ` Felipe Contreras
2010-11-02  0:14 ` [PATCH v3 2/2] drivers: cleanup Kconfig stuff Felipe Contreras
2010-11-02  0:14   ` Felipe Contreras
2010-11-02 13:11   ` Mark Brown
2010-11-02 13:11     ` Mark Brown
2010-11-02 14:02     ` Felipe Contreras
2010-11-02 14:02       ` Felipe Contreras
2010-11-02 14:12       ` Uwe Kleine-König
2010-11-02 14:12         ` Uwe Kleine-König
2010-11-02 14:18         ` Felipe Contreras
2010-11-02 14:18           ` Felipe Contreras
2010-11-02 14:39           ` Mark Brown [this message]
2010-11-02 14:39             ` Mark Brown
2010-11-02 19:46             ` Felipe Contreras
2010-11-02 20:34               ` Mark Brown
2010-11-02 14:35       ` Mark Brown
2010-11-02 19:43         ` Felipe Contreras
2010-11-02 19:43           ` Felipe Contreras
2010-11-02 20:26           ` Mark Brown
2010-11-02 14:14   ` Uwe Kleine-König
2010-11-02 14:14     ` Uwe Kleine-König
2010-11-02 14:23     ` Felipe Contreras
2010-11-02 14:23       ` Felipe Contreras

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=20101102143949.GH21476@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@linux.intel.com \
    --cc=balbi@ti.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=felipe.contreras@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=hao.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=mike@compulab.co.il \
    --cc=sameo@linux.intel.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.