From: Bamvor Jian Zhang <bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org,
khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org,
Bamvor Jian Zhang
<bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: [PATCH V2 0/3] Clean up and enable two testcases in kselftest
Date: Tue, 17 Nov 2015 22:35:40 +0800 [thread overview]
Message-ID: <1447770943-10059-1-git-send-email-bamvor.zhangjian@linaro.org> (raw)
These patches try to enable two testcases (capabilities and ipc) and
make them build successful in cross compiling environment.
Clean up the Makefile of capabilities according to the usage in
kselftest.
Changes since v1
1. Update Makefile of capabilities according to Michael's suggestion.
reference commit message for details.
Bamvor Jian Zhang (3):
selftests/capabilities: clean up for Makefile
selftests/capabilities: actually test it
selftest/ipc: actually test it
tools/testing/selftests/Makefile | 2 ++
tools/testing/selftests/capabilities/Makefile | 21 +++++++++------------
2 files changed, 11 insertions(+), 12 deletions(-)
--
1.8.4.5
next reply other threads:[~2015-11-17 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 14:35 Bamvor Jian Zhang [this message]
[not found] ` <1447770943-10059-1-git-send-email-bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-17 14:35 ` [PATCH V2 1/3] selftests/capabilities: clean up for Makefile Bamvor Jian Zhang
2015-11-17 14:35 ` [PATCH V2 2/3] selftests/capabilities: actually test it Bamvor Jian Zhang
2015-11-17 14:35 ` [PATCH V2 3/3] selftest/ipc: " Bamvor Jian Zhang
2015-11-23 20:33 ` [PATCH V2 0/3] Clean up and enable two testcases in kselftest 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=1447770943-10059-1-git-send-email-bamvor.zhangjian@linaro.org \
--to=bamvor.zhangjian-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org \
--cc=shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
--cc=tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).