From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix a typo in drivers/acpi/battery.c
Date: Sun, 13 Dec 2009 16:23:18 -0800 [thread overview]
Message-ID: <4B258576.3070508@gmail.com> (raw)
In-Reply-To: <20091213151545.4ac17532.rdunlap@xenotime.net>
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@gmail.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@vger.kernel.org .
>
> ---
> ~Randy
>
So should I resend this to acpi then, or just
take note of this the next time?
Justin P. Mattock
next prev parent reply other threads:[~2009-12-14 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 22:48 Fix-a-typo-in-battery.c Justin P. Mattock
2009-12-13 22:48 ` [PATCH] Fix a typo in drivers/acpi/battery.c Justin P. Mattock
2009-12-13 23:15 ` Randy Dunlap
2009-12-14 0:23 ` Justin P. Mattock [this message]
2009-12-14 1:21 ` Randy Dunlap
2009-12-14 2:35 ` Justin P. Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B258576.3070508@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox