From: Balbir Singh <bsingharora@gmail.com>
To: mpe@ellerman.id.au, npiggin@gmail.com, mahesh@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, Balbir Singh <bsingharora@gmail.com>
Subject: [PATCH v2 2/5] powerpc/mce: align the print of physical address better
Date: Wed, 13 Sep 2017 16:10:46 +1000 [thread overview]
Message-ID: <20170913061049.13256-3-bsingharora@gmail.com> (raw)
In-Reply-To: <20170913061049.13256-1-bsingharora@gmail.com>
Use the same alignment as Effective address and rename
phyiscal address to Page Frame Number
Signed-off-by: Balbir Singh <bsingharora@gmail.com>
---
arch/powerpc/kernel/mce.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/mce.c b/arch/powerpc/kernel/mce.c
index e254399..f351adf 100644
--- a/arch/powerpc/kernel/mce.c
+++ b/arch/powerpc/kernel/mce.c
@@ -340,7 +340,7 @@ void machine_check_print_event_info(struct machine_check_event *evt,
printk("%s Effective address: %016llx\n",
level, evt->u.ue_error.effective_address);
if (evt->u.ue_error.physical_address_provided)
- printk("%s Physical address: %016llx\n",
+ printk("%s Page Frame Number: %016llx\n",
level, evt->u.ue_error.physical_address);
break;
case MCE_ERROR_TYPE_SLB:
--
2.9.5
next prev parent reply other threads:[~2017-09-13 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 6:10 [PATCH v2 0/4] Revisit MCE handling for UE Errors Balbir Singh
2017-09-13 6:10 ` [PATCH v2 1/5] powerpc/mce.c: Remove unused function get_mce_fault_addr() Balbir Singh
2017-09-13 6:10 ` Balbir Singh [this message]
2017-09-13 6:10 ` [PATCH v2 3/5] powerpc/mce: Hookup derror (load/store) UE errors Balbir Singh
2017-09-13 6:21 ` Nicholas Piggin
2017-09-13 6:26 ` Balbir Singh
2017-09-13 8:56 ` Nicholas Piggin
2017-09-13 6:10 ` [PATCH v2 4/5] powerpc/mce: Hookup ierror (instruction) " Balbir Singh
2017-09-13 6:10 ` [PATCH v2 5/5] powerpc/mce: hookup memory_failure for " Balbir Singh
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=20170913061049.13256-3-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).