linux-kernel - Re: [PATCH] acpi: Update battery information on notification 0x81

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201101032156.24402.rjw@sisk.pl>
Date:	Mon, 3 Jan 2011 21:56:24 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	lenb@...nel.org
Subject: Re: [PATCH] acpi: Update battery information on notification 0x81

On Monday, January 03, 2011, Matthew Garrett wrote:
> On Thu, Dec 23, 2010 at 11:23:42PM +0100, Rafael J. Wysocki wrote:
> 
> > As I've already said on IRC, I'd simply add a new function like:
> > 
> > void acpi_battery_refresh(struct acpi_battery *battery)
> > {
> > 	if (!battery->bat.dev)
> > 		return;
> > 	acpi_battery_get_info(battery);
> > 	/* The battery may have changed its reporting units */
> > 	sysfs_remove_battery(battery);
> > 	sysfs_add_battery(battery);
> > }
> > 
> > and call it before acpi_battery_update()
> > (a) in acpi_battery_resume()
> > (b) in acpi_battery_notify() if event == ACPI_BATTERY_NOTIFY_INFO
> > 
> > That would be more straightforward IMHO.
> 
> That might be more reasonable. Want to send that, or shall I?

I can do that.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/