From: Andrew Morton <akpm@digeo.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: torvalds@transmeta.com, acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] acpismp=force fix
Date: Mon, 23 Jun 2003 00:58:57 -0700 [thread overview]
Message-ID: <20030623005857.06c76dbd.akpm@digeo.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A302@orsmsx401.jf.intel.com>
"Grover, Andrew" <andrew.grover@intel.com> wrote:
>
> Does anyone have a reason why acpismp=force should be in 2.5/6?
I can't think of one.
> If not I'll go ahead and zap it (again)
zap away. Dave Jones is maintaining a "stuff which changed" document.
Please send him a paragraph.
next prev parent reply other threads:[~2003-06-23 7:44 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
2003-06-23 7:58 ` Andrew Morton [this message]
2003-06-23 8:01 ` Arjan van de Ven
2003-06-23 11:46 ` Hugh Dickins
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
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=20030623005857.06c76dbd.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=acpi-devel@lists.sourceforge.net \
--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