From: Denis Efremov <efremov@linux.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Russell King <linux@armlinux.org.uk>
Cc: Denis Efremov <efremov@linux.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: [PATCH 1/2] ARM: makefile: Drop GZFLAGS definition and export
Date: Fri, 4 Sep 2020 23:12:57 +0300 [thread overview]
Message-ID: <20200904201258.795438-2-efremov@linux.com> (raw)
In-Reply-To: <20200904201258.795438-1-efremov@linux.com>
Drop the definition and export of GZFLAGS, because it's
not used. GZFLAGS was dropped from arm64 in commit
4cf234943dcf ("arm64: drop GZFLAGS definition and export").
Signed-off-by: Denis Efremov <efremov@linux.com>
---
arch/arm/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index 4e877354515f..3780063e0be0 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -20,7 +20,6 @@ ifeq ($(CONFIG_ARM_MODULE_PLTS),y)
KBUILD_LDS_MODULE += $(srctree)/arch/arm/kernel/module.lds
endif
-GZFLAGS :=-9
#KBUILD_CFLAGS +=-pipe
# Never generate .eh_frame
@@ -270,7 +269,7 @@ KBUILD_CPPFLAGS += $(patsubst %,-I$(srctree)/%include,$(machdirs) $(platdirs))
endif
endif
-export TEXT_OFFSET GZFLAGS MMUEXT
+export TEXT_OFFSET MMUEXT
core-y += arch/arm/
# If we have a machine-specific directory, then include it in the build.
--
2.26.2
next prev parent reply other threads:[~2020-09-04 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 20:12 [PATCH 0/2] drop GZFLAGS definition Denis Efremov
2020-09-04 20:12 ` Denis Efremov [this message]
2020-09-05 16:46 ` [PATCH 1/2] ARM: makefile: Drop GZFLAGS definition and export Masahiro Yamada
2020-09-04 20:12 ` [PATCH 2/2] csky: Drop GZFLAGS definition Denis Efremov
2020-09-05 16:46 ` Masahiro Yamada
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=20200904201258.795438-2-efremov@linux.com \
--to=efremov@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masahiroy@kernel.org \
--subject='Re: [PATCH 1/2] ARM: makefile: Drop GZFLAGS definition and export' \
/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
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).