The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 0/3] selftests: gpio: fix minor build issues
Date: Mon,  8 Nov 2021 09:28:48 +0800	[thread overview]
Message-ID: <20211108012851.7772-1-warthog618@gmail.com> (raw)

This is a series of fixes for minor problems in the building of the GPIO
selftests introduced by my rework of those tests.

The first patch is from Li Zhijian and fixes a compiler error when
building the selftests in environments with stale system includes.
I have reworded the commit comment to make it more to the point in
describing the root cause of the problem and the fix, as suggested by
Shuah in his initial review of that patch.

The second patch fixes a warning when the tests are compiled with -Wall,
and the final patch restores the CFLAGS that should not have been removed
in the rework, including the -Wall.

Kent Gibson (2):
  selftests: gpio: fix uninitialised variable warning
  selftests: gpio: restore CFLAGS options

Li Zhijian (1):
  selftests: gpio: fix gpio compiling error

 tools/testing/selftests/gpio/Makefile           | 1 +
 tools/testing/selftests/gpio/gpio-mockup-cdev.c | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.33.1


             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 Kent Gibson [this message]
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 ` [PATCH 3/3] selftests: gpio: restore CFLAGS options Kent Gibson
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-1-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