All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
	"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH 0/4] x86/fpu/state: Fix XSAVES issues - Part 1
Date: Fri, 20 May 2016 19:41:20 +0200	[thread overview]
Message-ID: <20160520174120.GB9970@gmail.com> (raw)
In-Reply-To: <20160520154111.GA18575@test-lenovo>


* Yu-cheng Yu <yu-cheng.yu@intel.com> wrote:

> On Fri, May 20, 2016 at 09:12:00AM +0200, Ingo Molnar wrote:
> > Hm, the series does not apply cleanly:
> > 
> >  patching file arch/x86/include/asm/fpu/xstate.h
> >  patching file arch/x86/include/asm/processor.h
> >  patching file arch/x86/kernel/fpu/init.c
> >  patching file arch/x86/kernel/fpu/signal.c
> >  patching file arch/x86/kernel/fpu/xstate.c
> >  Hunk #4 FAILED at 552.
> >  1 out of 6 hunks FAILED -- rejects in file arch/x86/kernel/fpu/xstate.c
> > 
> > which suggests that this series isn't against a recent x86 tree, right?
> 
> That was based on the latest upstream kernel.  I also keep a version based
> on tip/master.  Would it work?

Yes, tip/master would be fine, or upstream bc231d9ede99 that has the x86 tree 
already merged.

Thanks,

	Ingo.

  reply	other threads:[~2016-05-20 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 16:34 [PATCH 0/4] x86/fpu/state: Fix XSAVES issues - Part 1 Yu-cheng Yu
2016-05-12 16:34 ` [PATCH 1/4] x86/fpu/xstate: Define and use fpu_user_xstate_size Yu-cheng Yu
2016-05-12 16:34 ` [PATCH 2/4] x86/fpu/xstate: Rename xstate_size to fpu_kernel_xstate_size to distinguish from fpu_user_xstate_size Yu-cheng Yu
2016-05-12 16:34 ` [PATCH 3/4] x86/fpu/xstate: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization Yu-cheng Yu
2016-05-12 16:34 ` [PATCH 4/4] x86/fpu/xstate: Copy xstate registers directly to signal frame when compacted format is in use Yu-cheng Yu
2016-05-20  7:12 ` [PATCH 0/4] x86/fpu/state: Fix XSAVES issues - Part 1 Ingo Molnar
2016-05-20 15:41   ` Yu-cheng Yu
2016-05-20 17:41     ` Ingo Molnar [this message]
2016-05-20 16:50   ` Yu-cheng Yu
2016-05-20 17:47 Yu-cheng Yu

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=20160520174120.GB9970@gmail.com \
    --to=mingo@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=ravi.v.shankar@intel.com \
    --cc=sai.praneeth.prakhya@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yu-cheng.yu@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.