From: Andrey Panin <pazke@donpac.ru>
To: akpm <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] VISWS: prevent APM
Date: Thu, 2 Dec 2004 08:50:20 +0300 [thread overview]
Message-ID: <20041202055020.GC20380@pazke> (raw)
In-Reply-To: <20041201115758.294585c3.rddunlap@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
On 336, 12 01, 2004 at 11:57:58AM -0800, Randy.Dunlap wrote:
> (resend)
>
> Prevent X86_VISWS config from building APM support.
> APM isn't supported and it won't build if attempted.
> Also disable P4THERMAL for VISWS.
>
> Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Look good. Please apply.
Signed-off-by: Andrey Panin <pazke@donpac.ru>
> diffstat:=
> arch/i386/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff -Naurp ./arch/i386/Kconfig~visws_noapm ./arch/i386/Kconfig
> --- ./arch/i386/Kconfig~visws_noapm 2004-10-11 10:54:31.019559744 -0700
> +++ ./arch/i386/Kconfig 2004-10-14 09:52:24.131743344 -0700
> @@ -584,7 +584,7 @@ config X86_MCE_NONFATAL
>
> config X86_MCE_P4THERMAL
> bool "check for P4 thermal throttling interrupt."
> - depends on X86_MCE && (X86_UP_APIC || SMP)
> + depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
> help
> Enabling this feature will cause a message to be printed when the P4
> enters thermal throttling.
> @@ -879,7 +879,7 @@ source kernel/power/Kconfig
> source "drivers/acpi/Kconfig"
>
> menu "APM (Advanced Power Management) BIOS Support"
> -depends on PM
> +depends on PM && !X86_VISWS
>
> config APM
> tristate "APM (Advanced Power Management) BIOS support"
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-12-02 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 19:57 [PATCH] VISWS: prevent APM Randy.Dunlap
2004-12-02 5:50 ` Andrey Panin [this message]
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=20041202055020.GC20380@pazke \
--to=pazke@donpac.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.