From: "Yinghai Lu" <yinghai@kernel.org>
To: "Krzysztof Helt" <krzysztof.h1@poczta.fm>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
sfr@canb.auug.org.au, "Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: enable CPUID on Cyrix cpus with CPUID disabled
Date: Mon, 29 Sep 2008 10:56:29 -0700 [thread overview]
Message-ID: <86802c440809291056m7369062ft6b16d17299ca5701@mail.gmail.com> (raw)
In-Reply-To: <20080929192407.1c31fe90.krzysztof.h1@poczta.fm>
On Mon, Sep 29, 2008 at 10:24 AM, Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:
> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> The macros setCx86_old() and getCx86_old() do not
> work as a comment says in the processor-cyrix.h.
>
> Use working inline functions instead to enable
> the CPUID instriction on Cyrix cpus.
>
> Tested on IBM 6x86MX cpu with disabled the
> CPUID instruction.
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
> ---
>
> This patch is against the linux-next tree (20080819)
> as it contains the following patch:
>
> x86, cyrix: debug
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=026e2c05ef58ef413e2d52696f125d5ea1aa8bce
>
> The linux-2.6-tip tree has not the Ingo's patch so it
> does not require my patch.
>
> I am confused. Is the x86 detection code for Cyrix
> cpus is right in the linux-next or in the linux-2.6-tip?
> Should I prepare patches against the linux-2.6-tip
> or linux-next?
linux-2.6-tip.
YH
next prev parent reply other threads:[~2008-09-29 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 17:24 Krzysztof Helt
2008-09-29 17:56 ` Yinghai Lu [this message]
2008-09-30 9:43 ` Ingo Molnar
2008-09-30 13:06 krzysztof.h1
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=86802c440809291056m7369062ft6b16d17299ca5701@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--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
all inboxes | Powered by JetHome®