From: Jesse Barnes <jbarnes-sJ/iWh9BUns@public.gmane.org>
To: Jason Uhlenkott <jasonuhl-sJ/iWh9BUns@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Luck-S9ox3Mig+MlTNBMFyi6HDFaTQe2KTcn/@public.gmane.org,
Tony <tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: 2.6.12-rc1-mm3
Date: Fri, 25 Mar 2005 19:40:24 -0800 [thread overview]
Message-ID: <200503251940.24644.jbarnes@sgi.com> (raw)
In-Reply-To: <20050326025704.GE207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Friday, March 25, 2005 6:57 pm, Jason Uhlenkott wrote:
> On Fri, Mar 25, 2005 at 09:24:21PM -0500, Len Brown wrote:
> > What bad things happen if you define CONFIG_PM on SN2?
>
> None, other than slightly enlarging the kernel with some
> suspend/resume stuff we don't care about. It's always been
> unavailable for SN2 builds:
>
> depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB
>
> but there doesn't appear to be any particular reason for that other
> than us not needing it (and in fact SN2 systems can run IA64_GENERIC
> kernels with CONFIG_PM enabled without incident).
>
> > Re: CONFIG_ACPI_BOOT
> > I've got a patch that makes it go away -- this looks like
> > a good reason for me to dust it off... Looks like
> > arch/ia64/Kconfig defines ACPI and then pulls in drivers/acpi/Kconfig,
> > which it should not do - it should look like i386/Kconfig...
Yeah, I noticed that too. If you've got a patch to clean it up, we should go
ahead and get it sent off to Tony.
I sent this to linux-ia64 the other day to address these issues.
Jesse
[-- Attachment #2: ia64-kconfig-pm-fix.patch --]
[-- Type: text/x-diff, Size: 409 bytes --]
===== arch/ia64/Kconfig 1.85 vs edited =====
--- 1.85/arch/ia64/Kconfig 2005-01-28 15:32:25 -08:00
+++ edited/arch/ia64/Kconfig 2005-03-21 09:38:29 -08:00
@@ -328,7 +328,7 @@
config PM
bool "Power Management support"
- depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB
+ depends on !IA64_HP_SIM
default y
help
"Power Management" means that parts of your computer are shut
next prev parent reply other threads:[~2005-03-26 3:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050325002154.335c6b0b.akpm@osdl.org>
2005-03-26 1:43 ` 2.6.12-rc1-mm3 Jason Uhlenkott
[not found] ` <20050326014327.GB207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 1:56 ` 2.6.12-rc1-mm3 Len Brown
2005-03-26 2:02 ` [ACPI] " Jason Uhlenkott
[not found] ` <20050326020212.GC207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 2:24 ` Len Brown
2005-03-26 2:57 ` [ACPI] " Jason Uhlenkott
[not found] ` <20050326025704.GE207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 3:40 ` Jesse Barnes [this message]
2005-03-26 4:12 ` Len Brown
2005-03-26 5:52 ` Jason Uhlenkott
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=200503251940.24644.jbarnes@sgi.com \
--to=jbarnes-sj/iwh9buns@public.gmane.org \
--cc=Luck-S9ox3Mig+MlTNBMFyi6HDFaTQe2KTcn/@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=jasonuhl-sJ/iWh9BUns@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony.luck-ral2JQCrhuEAvxtiuMwx3w@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