From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, trivial@kernel.org,
Lin Ming <ming.m.lin@intel.com>, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] acpi: add missing newline to printk
Date: Fri, 02 Nov 2012 21:06:30 +0100 [thread overview]
Message-ID: <2755585.b9GScQZuQJ@vostro.rjw.lan> (raw)
In-Reply-To: <1351875078-5843-1-git-send-email-cesarb@cesarb.net>
On Friday, November 02, 2012 02:51:18 PM Cesar Eduardo Barros wrote:
> The missing newline causes messages like this on dmesg:
>
> [ 2.578212] ACPI: Invalid Power Resource to register!<5>[2.578456] ...
>
> Cc: Lin Ming <ming.m.lin@intel.com>
> Cc: Len Brown <len.brown@intel.com>
> Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
An equivalent patch has been applied already.
Thanks,
Rafael
> ---
> drivers/acpi/power.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
> index 40e38a0..7db61b8 100644
> --- a/drivers/acpi/power.c
> +++ b/drivers/acpi/power.c
> @@ -473,7 +473,7 @@ int acpi_power_resource_register_device(struct device *dev, acpi_handle handle)
> 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.
next prev parent reply other threads:[~2012-11-02 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:51 Cesar Eduardo Barros
2012-11-02 20:06 ` Rafael J. Wysocki [this message]
2018-04-10 17:10 [PATCH] ACPI: " Laszlo Toth
2018-05-09 9:54 ` Rafael J. Wysocki
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=2755585.b9GScQZuQJ@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cesarb@cesarb.net \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=trivial@kernel.org \
/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®