From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / power: add missing newline to debug messages
Date: Fri, 05 Jul 2013 14:18:14 +0200 [thread overview]
Message-ID: <2462906.A69BgWcTke@vostro.rjw.lan> (raw)
In-Reply-To: <1373015756-29635-1-git-send-email-mika.westerberg@linux.intel.com>
On Friday, July 05, 2013 12:15:56 PM Mika Westerberg wrote:
> There are few places in power.c where debug messages have no newline at the
> end. Reading such debug messages from dmesg is not fun so fix this by
> adding the missing newlines.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Applied, thanks!
Rafael
> ---
> drivers/acpi/power.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
> index 288bb27..5c28c89 100644
> --- a/drivers/acpi/power.c
> +++ b/drivers/acpi/power.c
> @@ -279,7 +279,7 @@ static int acpi_power_on_unlocked(struct acpi_power_resource *resource)
>
> if (resource->ref_count++) {
> ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> - "Power resource [%s] already on",
> + "Power resource [%s] already on\n",
> resource->name));
> } else {
> result = __acpi_power_on(resource);
> @@ -325,7 +325,7 @@ static int acpi_power_off_unlocked(struct acpi_power_resource *resource)
>
> if (!resource->ref_count) {
> ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> - "Power resource [%s] already off",
> + "Power resource [%s] already off\n",
> resource->name));
> return 0;
> }
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-07-05 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 9:15 Mika Westerberg
2013-07-05 12:18 ` 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=2462906.A69BgWcTke@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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
all inboxes | Powered by JetHome®