From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 18:46:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 049A716A41F; Tue, 26 Jul 2005 18:46:11 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1AF143D45; Tue, 26 Jul 2005 18:46:10 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j6QIk7o5016369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Jul 2005 11:46:10 -0700 Message-ID: <42E684EF.3030601@root.org> Date: Tue, 26 Jul 2005 11:46:07 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcin Jessa References: <42E1481F.5040306@root.org> <20050723133819.36efb537.lists@yazzy.org> <42E29CAA.1020007@root.org> <20050724215818.55f951ae.lists@yazzy.org> <42E42F10.3030309@root.org> <20050725091221.106a0368.lists@yazzy.org> <42E5134F.706@root.org> <20050726011943.0abe83a0.lists@yazzy.org> <42E5C96C.9060105@root.org> <20050726093317.522452a6.lists@yazzy.org> In-Reply-To: <20050726093317.522452a6.lists@yazzy.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: acpi battery rework patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 18:46:11 -0000 Marcin Jessa wrote: > On Mon, 25 Jul 2005 22:26:04 -0700 > Nate Lawson wrote: >>There is no bug here, this info is correct and matches the kernel >>behavior before my commit. So what is the buggy behavior? > > > In the first email i could not see the remining time when running on battery but then after a short while I sent one more email as reply to my own saying it showed up and this was propably becouse ACPI did not manage to get the battery state yet. > I dont know if there was any bug. I thought you had some issues so I tried to help. > It seems like we both wasted our time on a perfectly good code becouse you missed my second email :) Ok, thanks for clearing this up. No more info is necessary. -- Nate