linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Further sanitize INTEL_FAM6 naming
Date: Fri, 23 Aug 2019 10:12:47 +0200	[thread overview]
Message-ID: <20190823081247.GC2369@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190822205312.GA10757@agluck-desk2.amr.corp.intel.com>

On Thu, Aug 22, 2019 at 01:53:12PM -0700, Luck, Tony wrote:
> On Thu, Aug 22, 2019 at 12:23:06PM +0200, Peter Zijlstra wrote:
> > Lots of variation has crept in; time to collapse the lot again.
> 
> Conceptually good.  But I applied the series on top of tip/master
> and got a build error:
> 

> Looks like your scripts didn't anticipate the CPP gymnastics like:
> 
> #define VULNWL_INTEL(model, whitelist)          \
>         VULNWL(INTEL, 6, INTEL_FAM6_##model, whitelist)

Bah.. I'll go fix.

      parent reply	other threads:[~2019-08-23  8:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 10:23 [PATCH 0/5] Further sanitize INTEL_FAM6 naming Peter Zijlstra
2019-08-22 10:23 ` [PATCH 1/5] x86/intel: Aggregate big core client naming Peter Zijlstra
2019-08-26 11:46   ` [tip: x86/cpu] x86/cpu/intel: " tip-bot2 for Peter Zijlstra
2019-08-27  1:52     ` kbuild test robot
2019-08-22 10:23 ` [PATCH 2/5] x86/intel: Aggregate big core modile naming Peter Zijlstra
2019-08-26 11:46   ` [tip: x86/cpu] x86/cpu/intel: Aggregate big core mobile naming tip-bot2 for Peter Zijlstra
2019-08-22 10:23 ` [PATCH 3/5] x86/intel: Aggregate big core graphics naming Peter Zijlstra
2019-08-26 11:46   ` [tip: x86/cpu] x86/cpu/intel: " tip-bot2 for Peter Zijlstra
2019-08-22 10:23 ` [PATCH 4/5] x86/intel: Aggregate microserver naming Peter Zijlstra
2019-08-26  9:27   ` Ingo Molnar
2019-08-26  9:45     ` Peter Zijlstra
2019-08-26  9:55       ` Ingo Molnar
2019-08-26  9:46     ` Ingo Molnar
2019-08-26  9:48     ` Ingo Molnar
2019-08-26 11:46   ` [tip: x86/cpu] x86/cpu/intel: " tip-bot2 for Peter Zijlstra
2019-08-22 10:23 ` [PATCH 5/5] x86/intel: Add common OPTDIFFs Peter Zijlstra
2019-08-26 11:46   ` [tip: x86/cpu] x86/cpu/intel: " tip-bot2 for Peter Zijlstra
2019-08-22 20:53 ` [PATCH 0/5] Further sanitize INTEL_FAM6 naming Luck, Tony
2019-08-22 21:50   ` Luck, Tony
2019-08-23  8:12   ` Peter Zijlstra [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=20190823081247.GC2369@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@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).