From: Andy Lutomirski <luto@kernel.org>
To: Matthew Whitehead <tedheadster@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Andrew Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 0/2] x86/CPU: Use correct Cyrix-specific macros
Date: Sat, 16 Mar 2019 12:00:49 -0700 [thread overview]
Message-ID: <CALCETrWY+PsiHJdRFTAXp6yVJQJG0a08UBxrmZ-p=6XdNEZaig@mail.gmail.com> (raw)
In-Reply-To: <1552596361-8967-1-git-send-email-tedheadster@gmail.com>
On Thu, Mar 14, 2019 at 1:46 PM Matthew Whitehead <tedheadster@gmail.com> wrote:
>
> Replace the incorrect Cyrix-specific macro calls with the correct
> setCx86() and getCx86() calls. Also remove the unused setCx86_old(),
> getCx86_old() and their related comments in the code.
>
> Matthew Whitehead (2):
> x86/CPU: Use correct macros for Cyrix calls on Geode processors
> x86/CPU: Remove {get,set}Cx86_old macros used for Cyrix processors
This series looks reasonable to me. Also, Matthew seems to be the
best tester around for this old hardware, so, if he says it works, I
believe him :) I certainly can't test this stuff.
--Andy
next prev parent reply other threads:[~2019-03-16 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:45 [PATCH 0/2] x86/CPU: Use correct Cyrix-specific macros Matthew Whitehead
2019-03-14 20:46 ` [PATCH 1/2] x86/CPU: Use correct macros for Cyrix calls on Geode processors Matthew Whitehead
2019-03-21 11:40 ` [tip:x86/urgent] x86/cpu/cyrix: " tip-bot for Matthew Whitehead
2019-03-14 20:46 ` [PATCH 2/2] x86/CPU: Remove {get,set}Cx86_old macros used for Cyrix processors Matthew Whitehead
2019-03-21 11:40 ` [tip:x86/urgent] x86/cpu/cyrix: " tip-bot for Matthew Whitehead
2019-03-16 19:00 ` Andy Lutomirski [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-06 20:49 [PATCH 0/2] x86/CPU: Use correct Cyrix-specific macros Matthew Whitehead
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='CALCETrWY+PsiHJdRFTAXp6yVJQJG0a08UBxrmZ-p=6XdNEZaig@mail.gmail.com' \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tedheadster@gmail.com \
--cc=tglx@linutronix.de \
/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).