From: Arjan van de Ven <arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andrew Morton <akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org>,
torvalds-Lhe3bsMrZseB+jHODAdFcQ@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [BK PATCH] acpismp=force fix
Date: 23 Jun 2003 10:01:42 +0200 [thread overview]
Message-ID: <1056355301.1699.6.camel@laptop.fenrus.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A302-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On Mon, 2003-06-23 at 09:43, Grover, Andrew wrote:
> > From: Andrew Morton [mailto:akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org]
> > > ACPI: make it so acpismp=force works (reported by Andrew Morton)
>
> > But prior to 2.5.72, CPU enumeration worked fine without
> > acpismp=force.
> > Now it is required. How come?
>
> (I'm taking the liberty to update the subject, which I accidentally left
> blank)
>
> Because 2.4 has that behavior. One objection that people raised to
> applying the 2.4 ACPI patch was that it changed that behavior. So I made
> an effort to keep it there.
in 2.4 it is absolutely not mantadory; it's default actually if the cpu
advertises the "ht" flag.....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-23 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 7:43 [BK PATCH] acpismp=force fix Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A302-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-06-23 7:58 ` Andrew Morton
2003-06-23 8:01 ` Arjan van de Ven [this message]
[not found] ` <1056355301.1699.6.camel-PDvaWZGbcxi0rsOeZxrteAC/G2K4zDHf@public.gmane.org>
2003-06-23 11:46 ` Hugh Dickins
[not found] ` <Pine.LNX.4.44.0306231224590.1648-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-06-23 11:54 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 21:37 Brown, Len
[not found] ` <A5974D8E5F98D511BB910002A50A66470B981205-MgY+aF+eRfZviC08c4yzC1DQ4js95KgL@public.gmane.org>
2003-06-27 11:58 ` Hugh Dickins
[not found] ` <Pine.LNX.4.44.0306271221110.1197-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-06-27 11:59 ` Arjan van de Ven
2003-06-30 15:42 ` Juan Quintela
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=1056355301.1699.6.camel@laptop.fenrus.com \
--to=arjanv-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-LL/9OlyS9hIAvxtiuMwx3w@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-Lhe3bsMrZseB+jHODAdFcQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox