From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-sgx@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Cedric Xing <cedric.xing@intel.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: [PATCH 0/6] Fix the reported SGX selftest makefile issues
Date: Fri, 16 Aug 2019 20:23:41 +0300 [thread overview]
Message-ID: <20190816172347.32561-1-jarkko.sakkinen@linux.intel.com> (raw)
Cedric Xing reported various issues, which are hopefully taken care by
these patches. In addition, it removes the bindings from x86/Makefile as
it makes sense to split that into a separate commit.
Cc: Cedric Xing <cedric.xing@intel.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Jarkko Sakkinen (6):
selftests/x86/sgx: Fix objcopy call in the Makefile
selftests/x86/sgx: Do not generate object files
selftests/x86/sgx: Add -I$(OUTPUT) when compiling encl_piggy.S
selftests/x86/sgx: Fix EXTRA_CLEAN
selftests/x86/sgx: Fix target in the Makefile
selftests/x86: Revert SGX changes
tools/testing/selftests/x86/Makefile | 10 -------
tools/testing/selftests/x86/sgx/Makefile | 33 +++++++++++++-----------
tools/testing/selftests/x86/sgx/encl.lds | 1 +
3 files changed, 19 insertions(+), 25 deletions(-)
--
2.20.1
next reply other threads:[~2019-08-16 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 17:23 Jarkko Sakkinen [this message]
2019-08-16 17:23 ` [PATCH 1/6] selftests/x86/sgx: Fix objcopy call in the Makefile Jarkko Sakkinen
2019-08-16 17:23 ` [PATCH 2/6] selftests/x86/sgx: Do not generate object files Jarkko Sakkinen
2019-08-16 17:23 ` [PATCH 3/6] selftests/x86/sgx: Add -I$(OUTPUT) when compiling encl_piggy.S Jarkko Sakkinen
2019-08-16 17:23 ` [PATCH 4/6] selftests/x86/sgx: Fix EXTRA_CLEAN Jarkko Sakkinen
2019-08-16 17:23 ` [PATCH 5/6] selftests/x86/sgx: Fix target in the Makefile Jarkko Sakkinen
2019-08-16 17:23 ` [PATCH 6/6] selftests/x86: Revert SGX changes Jarkko Sakkinen
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=20190816172347.32561-1-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=cedric.xing@intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
/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).