archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <>
To: "Grover, Andrew" <>
Cc: ACPI-Devel mailing list <>,
	<>, Len Brown <>,
	Marcelo Tosatti <>
Subject: RE: ACPI patches updated (20030714)
Date: Tue, 15 Jul 2003 18:38:39 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307151832520.7904-100000@localhost.localdomain> (raw)
In-Reply-To: <>

On Tue, 15 Jul 2003, Grover, Andrew wrote:
> > From: Hugh Dickins [] 
> > > Make it so acpismp=force works (reported by Andrew Morton)
> > 
> > But we don't want "acpismp=force" to work, it now serves no purpose
> > but to confuse.  May I push again to Marcelo my patch you acked
> > before, which removes it completely?  I had been waiting to say it's
> > in 2.6, but Andrew didn't push it from 2.5-mm into 2.6 - any reason?
> > 
> > Whereas we would still like "noht" to work, but it's now beyond me.
> That patch was sitting in my bk tree but yeah it's kinda stale. Len
> Brown was going to completely redo all this stuff, so Hugh if you have a
> need for your fix in the interim then great feel free to push, but there
> is a more comprehensive fix also in the works.

I've no desperate need to push it, can easily apply the patch to my own
tree.  It's just that Marcelo is motoring so speedily towards 2.4.22,
be a shame if that goes out with CONFIG_ACPI_HT_ONLY needing pointless
"acpismp=force" too.  What's the schedule for Len's rework to Marcelo?


  reply	other threads:[~2003-07-15 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 17:21 ACPI patches updated (20030714) Grover, Andrew
2003-07-15 17:38 ` Hugh Dickins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-16 20:55 Mikael Pettersson
2003-07-16 20:36 Grover, Andrew
2003-07-16  9:47 Mikael Pettersson
2003-07-16  2:35 Brown, Len
2003-07-15 19:11 Grover, Andrew
2003-07-15 18:49 Mikael Pettersson
2003-07-15 18:07 Brown, Len
2003-07-15 19:02 ` Hugh Dickins
2003-07-15 16:53 Grover, Andrew
2003-07-15 17:11 ` Hugh Dickins
2003-07-15 17:57 ` Tugrul Galatali

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0307151832520.7904-100000@localhost.localdomain \ \ \ \ \ \ \

* 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).