From: Dave Hansen <dave.hansen@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/fpu] d91cab7813: CPU feature '(null)' is not supported.
Date: Thu, 08 Oct 2015 15:04:59 -0700 [thread overview]
Message-ID: <5616E88B.1010004@linux.intel.com> (raw)
In-Reply-To: <87io6hx5r2.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On 10/07/2015 10:56 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/fpu
> commit d91cab78133d33b1dfd3d3fa7167fcbf74fb5f99 ("x86/fpu: Rename XSAVE macros")
>
> The following new message is in kernel log with your commit.
>
> [ 6.237440] CPU feature '(null)' is not supported.
I think this is fixed by:
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=x86/fpu&id=158ecc39185b885420e5136b803b29be2bbec7fb
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@linux.intel.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Brian Gerst <brgerst@gmail.com>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [lkp] [x86/fpu] d91cab7813: CPU feature '(null)' is not supported.
Date: Thu, 8 Oct 2015 15:04:59 -0700 [thread overview]
Message-ID: <5616E88B.1010004@linux.intel.com> (raw)
In-Reply-To: <87io6hx5r2.fsf@yhuang-dev.intel.com>
On 10/07/2015 10:56 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/fpu
> commit d91cab78133d33b1dfd3d3fa7167fcbf74fb5f99 ("x86/fpu: Rename XSAVE macros")
>
> The following new message is in kernel log with your commit.
>
> [ 6.237440] CPU feature '(null)' is not supported.
I think this is fixed by:
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=x86/fpu&id=158ecc39185b885420e5136b803b29be2bbec7fb
next prev parent reply other threads:[~2015-10-08 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 5:56 [x86/fpu] d91cab7813: CPU feature '(null)' is not supported kernel test robot
2015-10-08 22:04 ` Dave Hansen [this message]
2015-10-08 22:04 ` [lkp] " Dave Hansen
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=5616E88B.1010004@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=lkp@lists.01.org \
/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.