public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	David Kershner <david.kershner@unisys.com>,
	sparmaintainer@unisys.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: unisys: change select to depends for subsystems
Date: Mon, 15 Jan 2018 15:54:22 +0100	[thread overview]
Message-ID: <20180115145422.GA4611@kroah.com> (raw)
In-Reply-To: <21c1422d-9941-6c1b-6ade-f66ac14fcc81@infradead.org>

On Sun, Jan 14, 2018 at 09:10:54PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Drivers should not 'select' a subsystem. Instead they should depend
> on it. If the subsystem is disabled, the user probably did that for
> a purpose and one driver shouldn't be changing that.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: David Kershner <david.kershner@unisys.com>
> Cc: sparmaintainer@unisys.com (Unisys internal)
> Cc: devel@driverdev.osuosl.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>  drivers/staging/unisys/Kconfig |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> --- lnx-415-rc8.orig/drivers/staging/unisys/Kconfig
> +++ lnx-415-rc8/drivers/staging/unisys/Kconfig
> @@ -4,8 +4,7 @@
>  menuconfig UNISYSSPAR
>  	bool "Unisys SPAR driver support"
>  	depends on X86_64 && !UML
> -	select PCI
> -	select ACPI
> +	depends on PCI && ACPI
>  	---help---
>  	Support for the Unisys SPAR drivers
>  

Does not apply to my tree at all :(

  reply	other threads:[~2018-01-15 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  5:10 [PATCH] staging: unisys: change select to depends for subsystems Randy Dunlap
2018-01-15 14:54 ` Greg Kroah-Hartman [this message]
2018-01-15 18:51   ` Randy Dunlap

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=20180115145422.GA4611@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=david.kershner@unisys.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sparmaintainer@unisys.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