From: Vladimir Murzin <vladimir.murzin@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: yamada.masahiro@socionext.com, linux-crypto@vger.kernel.org,
linux-kbuild@vger.kernel.org, kbuild-all@01.org
Subject: [RFC PATCH 0/4] Minor improvements over handling dependency on GAS
Date: Wed, 7 Nov 2018 09:40:04 +0000 [thread overview]
Message-ID: <1541583608-26375-1-git-send-email-vladimir.murzin@arm.com> (raw)
With recent changes in Kconfig processing it is now possible to expose
dependency on specific tools and supported options via Kconfig rather
than bury it deep in Makefile.
This small series try to address the case where the whole feature, for
instance arm64/lse or arm/crypto, depends on GAS.
Vladimir Murzin (4):
kconfig: add as-instr macro to scripts/Kconfig.include
arm64: lse: expose dependency on gas via Kconfig
arm64: turn "broken gas inst" into real config option
ARM: crypto: expose dependency on gas via Kconfig
arch/arm/crypto/Kconfig | 31 +++++++++++++++++++++----------
arch/arm/crypto/Makefile | 31 ++++++-------------------------
arch/arm64/Kconfig | 4 ++++
arch/arm64/Makefile | 18 ++----------------
arch/arm64/include/asm/atomic.h | 2 +-
arch/arm64/include/asm/lse.h | 6 +++---
arch/arm64/kernel/cpufeature.c | 4 ++--
scripts/Kconfig.include | 4 ++++
8 files changed, 43 insertions(+), 57 deletions(-)
--
1.9.1
next reply other threads:[~2018-11-07 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 9:40 Vladimir Murzin [this message]
2018-11-07 9:40 ` [RFC PATCH 1/4] kconfig: add as-instr macro to scripts/Kconfig.include Vladimir Murzin
2018-11-07 14:55 ` Will Deacon
2018-11-07 16:50 ` Vladimir Murzin
2018-11-07 9:40 ` [RFC PATCH 2/4] arm64: lse: expose dependency on gas via Kconfig Vladimir Murzin
2018-11-07 9:40 ` [RFC PATCH 3/4] arm64: turn "broken gas inst" into real config option Vladimir Murzin
2018-11-07 9:40 ` [RFC PATCH 4/4] ARM: crypto: expose dependency on gas via Kconfig Vladimir Murzin
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=1541583608-26375-1-git-send-email-vladimir.murzin@arm.com \
--to=vladimir.murzin@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.masahiro@socionext.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