From: Prarit Bhargava <prarit@redhat.com>
To: linux-acpi@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>
Subject: [RESEND PATCH] acpi/apei/erst: Remove "Error" from initialization and disable output
Date: Wed, 24 May 2017 11:30:38 -0400 [thread overview]
Message-ID: <1495639838-28099-1-git-send-email-prarit@redhat.com> (raw)
Sent a few weeks back ... no reply.
P.
---8<---
The word "Error" is used by many QA groups and users as a keyword to
indicate that there is a critical failure during system bootup. The ESRT
code would interact better with these scripts if the word "Error" was
dropped from non-error messages. Other ACPI features only use the acronym
for initialization and disable messages so the ESRT code should do the
same.
Remove "Error Record Serialization Table" and replace it with "ACPI ESRT"
in the messages.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Anton Vorontsov <anton@enomsg.org>
Cc: Colin Cross <ccross@android.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>
---
drivers/acpi/apei/erst.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/acpi/apei/erst.c b/drivers/acpi/apei/erst.c
index ec4f507b524f..a796b9d91e20 100644
--- a/drivers/acpi/apei/erst.c
+++ b/drivers/acpi/apei/erst.c
@@ -1129,8 +1129,7 @@ static int __init erst_init(void)
goto err;
if (erst_disable) {
- pr_info(
- "Error Record Serialization Table (ERST) support is disabled.\n");
+ pr_info("ACPI ERST support is disabled.\n");
goto err;
}
@@ -1187,8 +1186,7 @@ static int __init erst_init(void)
if (!erst_erange.vaddr)
goto err_release_erange;
- pr_info(
- "Error Record Serialization Table (ERST) support is initialized.\n");
+ pr_info("ACPI ERST support is initialized.\n");
buf = kmalloc(erst_erange.size, GFP_KERNEL);
spin_lock_init(&erst_info.buf_lock);
--
1.7.9.3
next reply other threads:[~2017-05-24 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 15:30 Prarit Bhargava [this message]
2017-05-24 16:27 ` [RESEND PATCH] acpi/apei/erst: Remove "Error" from initialization and disable output Kees Cook
2017-07-17 15:20 ` Prarit Bhargava
2017-07-17 23:21 ` Rafael J. Wysocki
2017-07-18 2:15 ` Huang, Ying
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=1495639838-28099-1-git-send-email-prarit@redhat.com \
--to=prarit@redhat.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@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