From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 22 13:16:11 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1C191065678; Sun, 22 Jun 2008 13:16:11 +0000 (UTC) (envelope-from dan@obluda.cz) Received: from fw.ax.cz (195.22.43.87.adsl.nextra.cz [195.22.43.87]) by mx1.freebsd.org (Postfix) with ESMTP id 581588FC0A; Sun, 22 Jun 2008 13:16:10 +0000 (UTC) (envelope-from dan@obluda.cz) Received: from [127.0.0.1] (vlasta.hide.ax.cz [172.20.1.4]) by fw.ax.cz (8.14.2/8.14.2) with ESMTP id m5MCn7nQ047221; Sun, 22 Jun 2008 14:49:09 +0200 (CEST) (envelope-from dan@obluda.cz) Message-ID: <485E4A3E.2050609@obluda.cz> Date: Sun, 22 Jun 2008 14:49:02 +0200 From: Dan Lukes Organization: SISAL, MFF UK User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Alan Cox References: <200806210630.m5L6U8rl051972@freefall.freebsd.org> In-Reply-To: <200806210630.m5L6U8rl051972@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080621-0, 21.06.2008), Outbound message X-Antivirus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, bug-followup@FreeBSD.org 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 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:16:12 -0000 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