public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"Jon Medhurst (Tixy)" <tixy@linaro.org>
Subject: [PATCH] firmware: arm_scpi: Add hardware dependencies
Date: Wed, 25 Jan 2017 14:32:00 +0100	[thread overview]
Message-ID: <20170125143200.0554ad0f@endymion> (raw)

With a name like that, I assume that the ARM SCPI protocol is only
useful on the ARM architectures.

Signed-off-by: Jean Delvare <jdelvare@suse.de>
Fixes: 8f1498c03d15 ("firmware: arm_scpi: make it depend on MAILBOX instead of")
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: Jon Medhurst (Tixy) <tixy@linaro.org>
---
Please correct me if I'm wrong.

 drivers/firmware/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-4.10-rc5.orig/drivers/firmware/Kconfig	2017-01-01 23:31:53.000000000 +0100
+++ linux-4.10-rc5/drivers/firmware/Kconfig	2017-01-25 14:19:36.875930416 +0100
@@ -21,6 +21,7 @@ config ARM_PSCI_CHECKER
 
 config ARM_SCPI_PROTOCOL
 	tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
+	depends on ARM || ARM64 || COMPILE_TEST
 	depends on MAILBOX
 	help
 	  System Control and Power Interface (SCPI) Message Protocol is


-- 
Jean Delvare
SUSE L3 Support

             reply	other threads:[~2017-01-25 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 13:32 Jean Delvare [this message]
2017-01-25 13:38 ` [PATCH] firmware: arm_scpi: Add hardware dependencies Sudeep Holla
2017-01-25 13:50   ` Jean Delvare
2017-01-25 13:56     ` Sudeep Holla
2017-01-25 14:14       ` Jean Delvare
2017-01-25 14:20         ` Sudeep Holla
2017-01-25 15:04           ` Jean Delvare
2017-01-25 15:15             ` Sudeep Holla
2017-01-27  8:53               ` Jean Delvare
2017-01-27  9:00                 ` Greg KH
2017-01-27 14:22                 ` Sudeep Holla

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=20170125143200.0554ad0f@endymion \
    --to=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=tixy@linaro.org \
    /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