linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@kernel.org>,
	Boris Petkov <bp@suse.de>,
	Dan Williams <dan.j.williams@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] x86/mce, PCI: Provide quirks to identify Xeon models with machine check recovery
Date: Fri, 26 Aug 2016 22:36:23 -0700	[thread overview]
Message-ID: <CA+55aFweMO6=K1Oyw_i0duRgZ2ushAqyCKLsyZ9Ou7X9zDrAhA@mail.gmail.com> (raw)
In-Reply-To: <20160827052634.GB19332@nazgul.tnic>

On Fri, Aug 26, 2016 at 10:26 PM, Borislav Petkov <bp@alien8.de> wrote:
>
> Shouldn't all that stuff below be in arch/x86/?
>
> arch/x86/pci/fixup.c maybe, for example?

Good catch.

As it's under a CONFIG_X86_64 test anyway, it looks to make a ton more
sense in the x86 pci fixup code.

                  Linus

  reply	other threads:[~2016-08-27  5:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1472244975.git.tony.luck@intel.com>
2016-08-27  5:21 ` [PATCH 0/4] Better memcpy_mcsafe() Borislav Petkov
     [not found] ` <dc51c61a114c713cb3eb645481f4bfd07a51408e.1472244975.git.tony.luck@intel.com>
2016-08-27  5:26   ` [PATCH 2/4] x86/mce, PCI: Provide quirks to identify Xeon models with machine check recovery Borislav Petkov
2016-08-27  5:36     ` Linus Torvalds [this message]
2016-08-30 18:53       ` [PATCH V2 " Luck, Tony
2016-09-01 12:38         ` Borislav Petkov
2016-09-01 16:34           ` Luck, Tony
2016-08-27  7:28 ` [PATCH 0/4] Better memcpy_mcsafe() Ingo Molnar

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='CA+55aFweMO6=K1Oyw_i0duRgZ2ushAqyCKLsyZ9Ou7X9zDrAhA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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).