From: Kent Gibson <warthog618@gmail.com>
To: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kselftest@vger.kernel.org, brgl@bgdev.pl,
linus.walleij@linaro.org, shuah@kernel.org, bamv2005@gmail.com,
lizhijian@cn.fujitsu.com
Cc: Kent Gibson <warthog618@gmail.com>
Subject: [PATCH 3/3] selftests: gpio: restore CFLAGS options
Date: Mon, 8 Nov 2021 09:28:51 +0800 [thread overview]
Message-ID: <20211108012851.7772-4-warthog618@gmail.com> (raw)
In-Reply-To: <20211108012851.7772-1-warthog618@gmail.com>
All the CFLAGS options were incorrectly removed in the recent rework
of the GPIO selftests. While some of the flags were specific to the old
implementation the remainder are still relevant. Restore those options.
Signed-off-by: Kent Gibson <warthog618@gmail.com>
---
tools/testing/selftests/gpio/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/gpio/Makefile b/tools/testing/selftests/gpio/Makefile
index 42ea7d2aa844..d7b312b44a62 100644
--- a/tools/testing/selftests/gpio/Makefile
+++ b/tools/testing/selftests/gpio/Makefile
@@ -3,6 +3,6 @@
TEST_PROGS := gpio-mockup.sh
TEST_FILES := gpio-mockup-sysfs.sh
TEST_GEN_PROGS_EXTENDED := gpio-mockup-cdev
-CFLAGS += -I../../../../usr/include
+CFLAGS += -O2 -g -Wall -I../../../../usr/include/
include ../lib.mk
--
2.33.1
next prev parent reply other threads:[~2021-11-08 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 1:28 [PATCH 0/3] selftests: gpio: fix minor build issues Kent Gibson
2021-11-08 1:28 ` [PATCH 1/3] selftests: gpio: fix gpio compiling error Kent Gibson
2021-11-08 1:28 ` [PATCH 2/3] selftests: gpio: fix uninitialised variable warning Kent Gibson
2021-11-08 1:28 ` Kent Gibson [this message]
2021-11-15 13:28 ` [PATCH 0/3] selftests: gpio: fix minor build issues Bartosz Golaszewski
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=20211108012851.7772-4-warthog618@gmail.com \
--to=warthog618@gmail.com \
--cc=bamv2005@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=shuah@kernel.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).