From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 22 13:20:04 2008 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36BB91065682 for ; Sun, 22 Jun 2008 13:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 231588FC17 for ; Sun, 22 Jun 2008 13:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5MDK3BX075093 for ; Sun, 22 Jun 2008 13:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5MDK3Il075092; Sun, 22 Jun 2008 13:20:03 GMT (envelope-from gnats) Date: Sun, 22 Jun 2008 13:20:03 GMT Message-Id: <200806221320.m5MDK3Il075092@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Dan Lukes Cc: Subject: Re: kern/120515: [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc wake memory X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Lukes List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2008 13:20:04 -0000 The following reply was made to PR kern/120515; it has been noted by GNATS. From: Dan Lukes To: Alan Cox Cc: freebsd-acpi@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: kern/120515: [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc wake memory Date: Sun, 22 Jun 2008 14:49:02 +0200 Alan Cox wrote: > new physical memory allocator in HEAD and RELENG_7 already addresses this problem in a systematic way. > > I see no reason not to apply this patch to RELENG_6. At the first, I analyzed problem for myself. My 6.x based instalations affected by the problem are hacked already as I decide not to wait several months for next release. Well, I offered the analysis and hack to the public also. To apply it into RELENG_6 or not apply it into RELENG_6 - it is commiters decision. I have no problem with either decision. Dan