linux-kernel - Re: [PATCH] Fix a typo in drivers/acpi/battery.c

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 13 Dec 2009 17:21:29 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix a typo in drivers/acpi/battery.c

On Sun, 13 Dec 2009 16:23:18 -0800 Justin P. Mattock wrote:

> On 12/13/09 15:15, Randy Dunlap wrote:
> > On Sun, 13 Dec 2009 14:48:56 -0800 Justin P. Mattock wrote:
> >
> >> Signed-off-by: Justin P. Mattock<justinmattock@...il.com>
> >> ---
> >>   drivers/acpi/battery.c |    2 +-
> >>   1 files changed, 1 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
> >> index 3f4602b..cada73f 100644
> >> --- a/drivers/acpi/battery.c
> >> +++ b/drivers/acpi/battery.c
> >> @@ -831,7 +831,7 @@ static void acpi_battery_notify(struct acpi_device *device, u32 event)
> >>   					dev_name(&device->dev), event,
> >>   					acpi_battery_present(battery));
> >>   #ifdef CONFIG_ACPI_SYSFS_POWER
> >> -	/* acpi_batter_update could remove power_supply object */
> >> +	/* acpi_battery_update could remove power_supply object */
> >>   	if (battery->bat.dev)
> >>   		kobject_uevent(&battery->bat.dev->kobj, KOBJ_CHANGE);
> >>   #endif
> >> --
> >
> > Hi,
> >
> > You don't need an intro patch email and then the patch email
> > for such a simple patch.
> >
> > Also, please note (from "MAINTAINERS" or from scripts/get_maintainer.pl)
> > that acpi patches go to linux-acpi@...r.kernel.org .
> >
> > ---
> > ~Randy
> >
> 
> So should I resend this to acpi then, or just
> take note of this the next time?

I'd say resend to linux-acpi and cc: the acpi maintainer.

---
~Randy
--
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/