From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
linux-acpi@vger.kernel.org, "Len Brown" <lenb@kernel.org>
Subject: Re: [PATCH] acpi: add newline in power.c message
Date: Fri, 02 Nov 2012 13:50:04 +0100 [thread overview]
Message-ID: <4807253.ASC2v3Jian@vostro.rjw.lan> (raw)
In-Reply-To: <508EBBFF.2020803@xenotime.net>
On Monday, October 29, 2012 10:25:19 AM Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Add newline to printk so that the message is on a line
> by itself and not merged with something unrelated to it.
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Reported-by: Toralf Förster <toralf.foerster@gmx.de>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>
Applied to the linux-next branch of the linux-pm.git tree as v3.8 material.
Thanks,
Rafael
> ---
> drivers/acpi/power.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-37-rc3.orig/drivers/acpi/power.c
> +++ lnx-37-rc3/drivers/acpi/power.c
> @@ -473,7 +473,7 @@ int acpi_power_resource_register_device(
> return ret;
>
> no_power_resource:
> - printk(KERN_DEBUG PREFIX "Invalid Power Resource to register!");
> + printk(KERN_DEBUG PREFIX "Invalid Power Resource to register!\n");
> return -ENODEV;
> }
> EXPORT_SYMBOL_GPL(acpi_power_resource_register_device);
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-11-02 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 18:44 cosmetic issue with error message 'Invalid Power Resource to register!' Toralf Förster
2012-10-29 17:25 ` [PATCH] acpi: add newline in power.c message Randy Dunlap
2012-10-30 20:34 ` Bjorn Helgaas
2012-11-02 12:50 ` Rafael J. Wysocki [this message]
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=4807253.ASC2v3Jian@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=toralf.foerster@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.