From: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
To: kernel-janitors@vger.kernel.org
Cc: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
Subject: [PATCH] arch: parisc: kernel: Remove DPRINTK definition and replace it with pr_debug
Date: Mon, 28 Jun 2021 23:18:55 +0200 [thread overview]
Message-ID: <20210628211855.89064-1-abd.masalkhi@gmail.com> (raw)
Removed the definition of DPRINTK macro and replaced it with pr_debug.
Signed-off-by: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
---
arch/parisc/kernel/pdc_chassis.c | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/arch/parisc/kernel/pdc_chassis.c b/arch/parisc/kernel/pdc_chassis.c
index 75ae88d13909..59433c50c58b 100644
--- a/arch/parisc/kernel/pdc_chassis.c
+++ b/arch/parisc/kernel/pdc_chassis.c
@@ -10,13 +10,6 @@
* Find out how to get Chassis warnings out of PAT boxes?
*/
-#undef PDC_CHASSIS_DEBUG
-#ifdef PDC_CHASSIS_DEBUG
-#define DPRINTK(fmt, args...) printk(fmt, ## args)
-#else
-#define DPRINTK(fmt, args...)
-#endif
-
#include <linux/init.h>
#include <linux/module.h>
#include <linux/kernel.h>
@@ -73,7 +66,7 @@ static void __init pdc_chassis_checkold(void)
default:
break;
}
- DPRINTK(KERN_DEBUG "%s: pdc_chassis_checkold(); pdc_chassis_old = %d\n", __FILE__, pdc_chassis_old);
+ pr_debug("%s: pdc_chassis_checkold(); pdc_chassis_old = %d\n", __FILE__, pdc_chassis_old);
}
#endif
@@ -126,7 +119,7 @@ void __init parisc_pdc_chassis_init(void)
{
#ifdef CONFIG_PDC_CHASSIS
if (likely(pdc_chassis_enabled)) {
- DPRINTK(KERN_DEBUG "%s: parisc_pdc_chassis_init()\n", __FILE__);
+ pr_debug("%s: parisc_pdc_chassis_init()\n", __FILE__);
/* Let see if we have something to handle... */
printk(KERN_INFO "Enabling %s chassis codes support v%s\n",
@@ -165,7 +158,7 @@ int pdc_chassis_send_status(int message)
#ifdef CONFIG_PDC_CHASSIS
if (likely(pdc_chassis_enabled)) {
- DPRINTK(KERN_DEBUG "%s: pdc_chassis_send_status(%d)\n", __FILE__, message);
+ pr_debug("%s: pdc_chassis_send_status(%d)\n", __FILE__, message);
#ifdef CONFIG_64BIT
if (is_pdc_pat()) {
--
2.29.0.rc1.dirty
reply other threads:[~2021-06-28 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210628211855.89064-1-abd.masalkhi@gmail.com \
--to=abd.masalkhi@gmail.com \
--cc=kernel-janitors@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