From: Axel Rasmussen <axelrasmussen@google.com>
To: Christian Brauner <brauner@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
llvm@lists.linux.dev, Axel Rasmussen <axelrasmussen@google.com>
Subject: [PATCH 2/2] selftests: fix an unused variable warning in pidfd selftest
Date: Thu, 24 Mar 2022 15:39:29 -0700 [thread overview]
Message-ID: <20220324223929.1893741-2-axelrasmussen@google.com> (raw)
In-Reply-To: <20220324223929.1893741-1-axelrasmussen@google.com>
I fixed a few warnings like this in commit e2aa5e650b07
("selftests: fixup build warnings in pidfd / clone3 tests"), but I
missed this one by mistake. Since this variable is unused, remove it.
Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
---
tools/testing/selftests/pidfd/pidfd_wait.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/pidfd/pidfd_wait.c b/tools/testing/selftests/pidfd/pidfd_wait.c
index 17999e082aa7..070c1c876df1 100644
--- a/tools/testing/selftests/pidfd/pidfd_wait.c
+++ b/tools/testing/selftests/pidfd/pidfd_wait.c
@@ -95,7 +95,6 @@ TEST(wait_states)
.flags = CLONE_PIDFD | CLONE_PARENT_SETTID,
.exit_signal = SIGCHLD,
};
- int ret;
pid_t pid;
siginfo_t info = {
.si_signo = 0,
--
2.35.1.1021.g381101b075-goog
next prev parent reply other threads:[~2022-03-24 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 22:39 [PATCH 1/2] selftests: fix header dependency for pid_namespace selftests Axel Rasmussen
2022-03-24 22:39 ` Axel Rasmussen [this message]
2022-03-25 15:21 ` [PATCH 2/2] selftests: fix an unused variable warning in pidfd selftest Christian Brauner
2022-03-25 19:50 ` Shuah Khan
2022-03-25 15:20 ` [PATCH 1/2] selftests: fix header dependency for pid_namespace selftests Christian Brauner
2022-03-25 19:50 ` Shuah Khan
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=20220324223929.1893741-2-axelrasmussen@google.com \
--to=axelrasmussen@google.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®