From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v25 0/3] x86/sgx: Fix feature control rebase
Date: Tue, 4 Feb 2020 07:26:16 +0200 [thread overview]
Message-ID: <20200204052616.GA14225@linux.intel.com> (raw)
In-Reply-To: <20200203200441.GD19638@linux.intel.com>
On Mon, Feb 03, 2020 at 12:04:41PM -0800, Sean Christopherson wrote:
> On Sun, Feb 02, 2020 at 12:18:04AM +0200, Jarkko Sakkinen wrote:
> > On Sat, Feb 01, 2020 at 09:35:59PM +0200, Jarkko Sakkinen wrote:
> > > If you fix any regression, use solely this tag as the baseline for
> > > fixes. I worry about possible merge conflicts with the master.
> > >
> > > /Jarkko
> >
> > As far as I'm concerned master has now everything for v25, so I removed
> > the tag. Just test against master.
>
> Sent a fix for the boot issue.
>
> Can you also rebase to Linus' latest tree? Or any tree that containts
> commit 8df5bb4a03b0 ("char: hpet: Fix out-of-bounds read bug"). Spent the
> morning bisecting another boot crash due to the hpet bug...
OK, I'll send the patch set today.
/Jarkko
prev parent reply other threads:[~2020-02-04 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 17:49 [PATCH for_v25 0/3] x86/sgx: Fix feature control rebase Sean Christopherson
2020-02-01 17:49 ` [PATCH for_v25 1/3] x86/msr: Fixup "Add Intel SGX hardware bits" Sean Christopherson
2020-02-01 17:49 ` [PATCH for_v25 2/3] x86/msr: Fixup "Intel SGX Launch Control " Sean Christopherson
2020-02-01 17:49 ` [PATCH for_v25 3/3] x86/cpu: Configure SGX support when initializing feature control MSR Sean Christopherson
2020-02-01 19:35 ` [PATCH for_v25 0/3] x86/sgx: Fix feature control rebase Jarkko Sakkinen
2020-02-01 22:18 ` Jarkko Sakkinen
2020-02-03 20:04 ` Sean Christopherson
2020-02-04 5:26 ` Jarkko Sakkinen [this message]
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=20200204052616.GA14225@linux.intel.com \
--to=jarkko.sakkinen@linux.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 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.