From: Nick Bowler <nbowler@elliptictech.com>
To: Borislav Petkov <bp@amd64.org>
Cc: "Jörg-Volker Peetz" <jvpeetz@web.de>,
"Boris Ostrovsky" <boris.ostrovsky@amd.com>,
"Andreas Herrmann" <andreas.herrmann3@amd.com>,
"Greg Kroah-Hartman" <greg@kroah.com>,
"Hans Rosenfeld" <hans.rosenfeld@amd.com>,
X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov" <borislav.petkov@amd.com>
Subject: Re: [PATCH 0/2] AMD ARAT fixes
Date: Tue, 17 May 2011 18:30:22 -0400 [thread overview]
Message-ID: <20110517223022.GA21342@elliptictech.com> (raw)
In-Reply-To: <1305636919-31165-1-git-send-email-bp@amd64.org>
On 2011-05-17 14:55 +0200, Borislav Petkov wrote:
> Although the patches look almost trivial, I'd like to ask Nick and
> Jörg-Volker to test them, please, so that we can have a confirmation,
> just in case.
Works as advertised, both patches applied on top of 2.6.38.6.
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-05-17 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:55 [PATCH 0/2] AMD ARAT fixes Borislav Petkov
2011-05-17 12:55 ` [PATCH 1/2] Revert "x86, AMD: Fix APIC timer erratum 400 affecting K8 Rev.A-E processors" Borislav Petkov
2011-05-17 12:55 ` [PATCH 2/2] x86, AMD: Fix ARAT feature setting again Borislav Petkov
2011-05-17 13:47 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2011-05-17 16:38 ` [PATCH 0/2] AMD ARAT fixes Jörg-Volker Peetz
2011-05-17 16:53 ` Borislav Petkov
2011-05-17 17:21 ` Jörg-Volker Peetz
2011-05-17 17:46 ` Borislav Petkov
2011-05-17 17:51 ` Jörg-Volker Peetz
2011-05-17 18:01 ` Borislav Petkov
2011-05-17 22:30 ` Nick Bowler [this message]
2011-05-18 6:51 ` Borislav Petkov
2011-05-18 15:50 ` Borislav Petkov
2011-05-20 14:37 ` Chuck Ebbert
2011-05-20 18:10 ` Boris Ostrovsky
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=20110517223022.GA21342@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=andreas.herrmann3@amd.com \
--cc=boris.ostrovsky@amd.com \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--cc=greg@kroah.com \
--cc=hans.rosenfeld@amd.com \
--cc=jvpeetz@web.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.