From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org (open list),
linux-arch@vger.kernel.org (open list:GENERIC INCLUDE/ASM HEADER
FILES), Dave Gerlach <d-gerlach@ti.com>,
Tony Lindgren <tony@atomide.com>, Keerthy J <j-keerthy@ti.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-omap@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>
Subject: [PATCH v3 4/4] misc: sram: Allow ARM64 to select SRAM_EXEC
Date: Fri, 16 Jun 2017 17:07:44 -0700 [thread overview]
Message-ID: <20170617000744.22158-5-f.fainelli@gmail.com> (raw)
In-Reply-To: <20170617000744.22158-1-f.fainelli@gmail.com>
Now that ARM64 also has a fncpy() implementation, allow selection
SRAM_EXEC for ARM64 as well.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
drivers/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 07bbd4cc1852..ac8779278c0c 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -464,7 +464,7 @@ config SRAM
bool "Generic on-chip SRAM driver"
depends on HAS_IOMEM
select GENERIC_ALLOCATOR
- select SRAM_EXEC if ARM
+ select SRAM_EXEC if ARM || ARM64
help
This driver allows you to declare a memory region to be managed by
the genalloc API. It is supposed to be used for small on-chip SRAM
--
2.9.3
next prev parent reply other threads:[~2017-06-17 0:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 0:07 [PATCH v3 0/4] Generalize fncpy availability Florian Fainelli
2017-06-17 0:07 ` [PATCH v3 1/4] ARM: fncpy: Rename include guards Florian Fainelli
2017-06-17 0:07 ` [PATCH v3 2/4] asm-generic: Provide a fncpy() implementation Florian Fainelli
2017-06-18 23:51 ` Yury Norov
2017-06-19 1:11 ` Yury Norov
2017-06-19 15:18 ` Yury Norov
2017-06-19 17:27 ` Florian Fainelli
2017-06-19 17:43 ` Russell King - ARM Linux
2017-06-20 14:27 ` Yury Norov
2017-06-19 20:58 ` Florian Fainelli
2017-06-20 14:24 ` Yury Norov
2017-06-17 0:07 ` [PATCH v3 3/4] arm64: Provide a fncpy implementation Florian Fainelli
2017-06-17 0:07 ` Florian Fainelli [this message]
2017-06-28 14:55 ` [PATCH v3 4/4] misc: sram: Allow ARM64 to select SRAM_EXEC Mark Rutland
2017-06-19 12:24 ` [PATCH v3 0/4] Generalize fncpy availability Mark Rutland
2017-06-19 13:53 ` Tony Lindgren
2017-06-19 17:32 ` Florian Fainelli
2017-06-20 9:10 ` Lorenzo Pieralisi
2017-06-20 16:20 ` Florian Fainelli
2017-06-20 16:46 ` Lorenzo Pieralisi
2017-06-20 16:54 ` Sudeep Holla
2017-06-20 17:03 ` Florian Fainelli
2017-06-19 13:34 ` David Howells
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=20170617000744.22158-5-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=d-gerlach@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=shawnguo@kernel.org \
--cc=tony@atomide.com \
--cc=will.deacon@arm.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