linux-sgx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-sgx@vger.kernel.org
Cc: haitao.huang@intel.com, serge.ayoun@intel.com,
	sean.j.christopherson@intel.com
Subject: Updated the GIT tree
Date: Tue, 6 Aug 2019 12:53:06 +0300	[thread overview]
Message-ID: <20190806095233.t3ap4acxofoswvc2@linux.intel.com> (raw)


Hi

I did some initial updates to prepare tree for v22 changes:

* Rebased https://github.com/intel/linux-sgx.git to v5.3-rc3.
* Fixed one merge conflict resulting from ioctl-number.txt being
  replaced with ioctl-number.rst.
* Removed changes from "x86/cpu/intel: Detect SGX support" that
  were leaked to the commit by mistake.
* Do not naturally align @addr and @len in sgx_get_unmapped_area().
* Check the kconfig flag INTEL_SGX_DRIVER in sgx_init() instead of
  defining two versions of sgx_drv_init().

/Jarkko

                 reply	other threads:[~2019-08-06  9:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190806095233.t3ap4acxofoswvc2@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=haitao.huang@intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=serge.ayoun@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).