mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: Andrew Morton <akpm@digeo.com>,
	torvalds@transmeta.com, acpi-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.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@orsmsx401.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Mon, 2003-06-23 at 09:43, Grover, Andrew wrote:
> > From: Andrew Morton [mailto:akpm@digeo.com] 
> > >    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 --]

  parent reply	other threads:[~2003-06-23  7:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23  7:43 Grover, Andrew
2003-06-23  7:58 ` Andrew Morton
2003-06-23  8:01 ` Arjan van de Ven [this message]
2003-06-23 11:46   ` Hugh Dickins
2003-06-23 11:54     ` Arjan van de Ven
2003-06-26 21:37 Brown, Len
2003-06-27 11:58 ` Hugh Dickins
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@redhat.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@digeo.com \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®