linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Felix Schnizlein <fschnizlein@suse.com>
Subject: Re: linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c)
Date: Mon, 25 Sep 2017 18:19:06 -0700	[thread overview]
Message-ID: <46a06a76-a17c-de77-362a-99a18efaee79@infradead.org> (raw)
In-Reply-To: <75e3d5e7-091e-9b26-47cc-36bece726b9e@infradead.org>

On 09/19/17 08:54, Randy Dunlap wrote:
> On 09/18/17 21:15, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20170918:
>>
>> Linus' tree still had its build failure for which I reverted a commit.
>>
> 
> on i386:
> 
> ../arch/x86/kernel/cpuinfo.c: In function 'cpuinfo_flags':
> ../arch/x86/kernel/cpuinfo.c:35:26: error: 'x86_cap_flags' undeclared (first use in this function)
>    if (cpu_has(cpu, i) && x86_cap_flags[i] != NULL)
>                           ^
> 
> # CONFIG_X86_FEATURE_NAMES is not set
> CONFIG_HAVE_CPUINFO_SYSFS=y
> 

Add author and driver-core maintainers.

Same error in linux-next 20170922.


-- 
~Randy

  reply	other threads:[~2017-09-26  1:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19  4:15 linux-next: Tree for Sep 19 Stephen Rothwell
2017-09-19 15:49 ` linux-next: Tree for Sep 19 (drivers/gpu/drm/i915/i915_gem.c) Randy Dunlap
2017-09-19 15:54 ` linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c) Randy Dunlap
2017-09-26  1:19   ` Randy Dunlap [this message]
2017-09-26  7:40     ` Thomas Gleixner
2017-09-26  8:18       ` Greg Kroah-Hartman
2017-09-26 10:40         ` Thomas Gleixner
2017-09-26 12:36           ` Felix Schnizlein
2017-09-26 16:00             ` Thomas Gleixner
2017-09-26 21:18               ` Greg Kroah-Hartman

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=46a06a76-a17c-de77-362a-99a18efaee79@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=fschnizlein@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.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 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).