From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc <linux-parisc@vger.kernel.org>
Subject: [PATCH 2/2] parisc: make the log level string for register dumps const
Date: Mon, 22 Jun 2020 20:52:32 +0200 [thread overview]
Message-ID: <1832606.jW6VkoSIHO@daneel.sf-tec.de> (raw)
In-Reply-To: <5385100.WkMxZrnbov@daneel.sf-tec.de>
Date: Mon, 22 Jun 2020 20:47:50 +0200
Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
---
arch/parisc/kernel/traps.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/parisc/kernel/traps.c b/arch/parisc/kernel/traps.c
index e6a0bfdf5c26..8e46428be70a 100644
--- a/arch/parisc/kernel/traps.c
+++ b/arch/parisc/kernel/traps.c
@@ -75,7 +75,7 @@ static int printbinary(char *buf, unsigned long x, int nbits)
lvl, f, (x), (x+3), (r)[(x)+0], (r)[(x)+1], \
(r)[(x)+2], (r)[(x)+3])
-static void print_gr(char *level, struct pt_regs *regs)
+static void print_gr(const char *level, struct pt_regs *regs)
{
int i;
char buf[64];
@@ -88,7 +88,7 @@ static void print_gr(char *level, struct pt_regs *regs)
PRINTREGS(level, regs->gr, "r", RFMT, i);
}
-static void print_fr(char *level, struct pt_regs *regs)
+static void print_fr(const char *level, struct pt_regs *regs)
{
int i;
char buf[64];
@@ -116,7 +116,7 @@ static void print_fr(char *level, struct pt_regs *regs)
void show_regs(struct pt_regs *regs)
{
int i, user;
- char *level;
+ const char *level;
unsigned long cr30, cr31;
user = user_mode(regs);
--
2.26.2
next prev parent reply other threads:[~2020-06-22 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 18:51 [PATCH 1/2] parisc: avoid needless empty lines inside register dump Rolf Eike Beer
2020-06-22 18:52 ` Rolf Eike Beer [this message]
2020-08-01 12:03 ` Rolf Eike Beer
2020-08-04 14:19 ` Helge Deller
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=1832606.jW6VkoSIHO@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.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;
as well as URLs for NNTP newsgroup(s).