From: aditya@kobol.io (Aditya Prayoga)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mvebu: Enable ARCH_WANT_LIBATA_LEDS in Armada 38x
Date: Wed, 19 Sep 2018 11:45:30 +0800 [thread overview]
Message-ID: <1537328730-9156-3-git-send-email-aditya@kobol.io> (raw)
In-Reply-To: <1537328730-9156-1-git-send-email-aditya@kobol.io>
Enable hidden symbol ARCH_WANT_LIBATA_LEDS so CONFIG_ATA_LEDS can be
used in kernel configuration.
URL: https://lists.openwrt.org/pipermail/openwrt-
devel/2017-March/006582.html
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
---
arch/arm/mach-mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 2c20599..51f3256 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -68,6 +68,7 @@ config MACH_ARMADA_38X
select HAVE_SMP
select MACH_MVEBU_V7
select PINCTRL_ARMADA_38X
+ select ARCH_WANT_LIBATA_LEDS
help
Say 'Y' here if you want your kernel to support boards based
on the Marvell Armada 380/385 SoC with device tree.
--
2.7.4
next prev parent reply other threads:[~2018-09-19 3:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 3:45 [PATCH 0/2] Add support per ATA port ledtrigger on armada 38x Aditya Prayoga
2018-09-19 3:45 ` [PATCH 1/2] libata: add ledtrig support Aditya Prayoga
2018-09-19 13:01 ` Andrew Lunn
2018-09-20 9:53 ` Aditya Prayoga
2018-09-19 18:36 ` kbuild test robot
2018-09-19 21:49 ` kbuild test robot
2018-09-19 21:49 ` [PATCH] libata: fix semicolon.cocci warnings kbuild test robot
2018-09-20 7:23 ` [PATCH 1/2] libata: add ledtrig support Pavel Machek
2018-09-20 8:24 ` Daniel Golle
2018-09-20 22:04 ` Pavel Machek
2018-09-21 6:31 ` Daniel Golle
2018-09-19 3:45 ` Aditya Prayoga [this message]
2018-09-20 7:26 ` [PATCH 2/2] ARM: mvebu: Enable ARCH_WANT_LIBATA_LEDS in Armada 38x Pavel Machek
2018-09-26 6:05 ` Aditya Prayoga
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=1537328730-9156-3-git-send-email-aditya@kobol.io \
--to=aditya@kobol.io \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).