All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-sgx@vger.kernel.org, serge.ayoun@intel.com,
	shay.katz-zamir@intel.com
Subject: Re: [PATCH v3 0/7] Fix the reported SGX selftest makefile issues
Date: Wed, 21 Aug 2019 20:31:59 -0700	[thread overview]
Message-ID: <20190822033158.GQ29345@linux.intel.com> (raw)
In-Reply-To: <20190819132830.9056-1-jarkko.sakkinen@linux.intel.com>

On Mon, Aug 19, 2019 at 04:28:23PM +0300, Jarkko Sakkinen wrote:
> Cedric Xing reported various issues in the selftest makefiles, which are
> hopefully taken care by these patches.
> 
> As the last patch this patch set contains a patch that implements the
> subdirectory traversal the for the x86 selftest directory tree. This
> patch is meant to be a separate patch in the main SGX patch set so that
> the bindings can be reviewed separately.

Doesn't have to be this series, but the build artifacts should be added
to .gitignore.

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        sgx/encl.ss
        sgx/sgxsign
        sgx/test_sgx

> 
> v3: 1,$s/SUB_DIRS/SUBDIRS/g
> v2: Added patch to implement the traversal to the subdirectories
>     selftest.
> 
> Jarkko Sakkinen (7):
>   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
>   selftests/x86: Recurse into subdirectories
> 
>  tools/testing/selftests/x86/Makefile     | 54 +++++++++++++++++++-----
>  tools/testing/selftests/x86/sgx/Makefile | 33 ++++++++-------
>  tools/testing/selftests/x86/sgx/encl.lds |  1 +
>  3 files changed, 63 insertions(+), 25 deletions(-)
> 
> -- 
> 2.20.1
> 

  parent reply	other threads:[~2019-08-22  3:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 13:28 [PATCH v3 0/7] Fix the reported SGX selftest makefile issues Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 1/7] selftests/x86/sgx: Fix objcopy call in the Makefile Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 2/7] selftests/x86/sgx: Do not generate object files Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 3/7] selftests/x86/sgx: Add -I$(OUTPUT) when compiling encl_piggy.S Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 4/7] selftests/x86/sgx: Fix EXTRA_CLEAN Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 5/7] selftests/x86/sgx: Fix target in the Makefile Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 6/7] selftests/x86: Revert SGX changes Jarkko Sakkinen
2019-08-19 13:28 ` [PATCH v3 7/7] selftests/x86: Recurse into subdirectories Jarkko Sakkinen
2019-08-22  3:42   ` Sean Christopherson
2019-08-22 14:59     ` Jarkko Sakkinen
2019-08-22 15:02       ` Jarkko Sakkinen
2019-08-22 16:13         ` Jarkko Sakkinen
2019-08-22 16:14           ` Jarkko Sakkinen
2019-08-22  3:31 ` Sean Christopherson [this message]
2019-08-22 14:58   ` [PATCH v3 0/7] Fix the reported SGX selftest makefile issues 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=20190822033158.GQ29345@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=serge.ayoun@intel.com \
    --cc=shay.katz-zamir@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.