From: Colin King <colin.king@canonical.com>
To: Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 4/5] ACPICA: GPE support: remove unnecessary newline from error messages
Date: Thu, 29 Nov 2012 11:53:15 +0000 [thread overview]
Message-ID: <1354189996-14431-5-git-send-email-colin.king@canonical.com> (raw)
In-Reply-To: <1354189996-14431-1-git-send-email-colin.king@canonical.com>
From: Colin Ian King <colin.king@canonical.com>
ACPI_ERROR() already appends a newline, so there is no
need for the error messages to include one too.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
drivers/acpi/acpica/hwgpe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/acpica/hwgpe.c b/drivers/acpi/acpica/hwgpe.c
index db40765..610ed72 100644
--- a/drivers/acpi/acpica/hwgpe.c
+++ b/drivers/acpi/acpica/hwgpe.c
@@ -134,7 +134,7 @@ acpi_hw_low_set_gpe(struct acpi_gpe_event_info *gpe_event_info, u32 action)
break;
default:
- ACPI_ERROR((AE_INFO, "Invalid GPE Action, %u\n", action));
+ ACPI_ERROR((AE_INFO, "Invalid GPE Action, %u", action));
return (AE_BAD_PARAMETER);
}
--
1.8.0
next prev parent reply other threads:[~2012-11-29 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 11:53 [PATCH 0/5] remove some " Colin King
2012-11-29 11:53 ` [PATCH 1/5] ACPI dock: remove unnecessary newline from exception message Colin King
2012-11-29 18:25 ` Toshi Kani
2012-11-29 11:53 ` [PATCH 2/5] ACPI video: remove unnecessary newline from error messages Colin King
2012-11-29 11:53 ` [PATCH 3/5] ACPI sysfs: remove unnecessary newline from exception Colin King
2012-11-29 11:53 ` Colin King [this message]
2012-11-29 11:53 ` [PATCH 5/5] ACPI thermal: remove unnecessary newline from exception message Colin King
2013-01-15 22:27 ` [PATCH 0/5] remove some unnecessary newline from error messages 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=1354189996-14431-5-git-send-email-colin.king@canonical.com \
--to=colin.king@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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®