summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>2026-04-27 20:45:46 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2026-05-15 05:04:50 +0300
commit2cc8a6cf8a801065b68550d5af33f62999ce15f0 (patch)
tree3e9501aa7a1fd05e5df093375b3b404954440815
parent250ba648f42d571e08e0bd95fa32953e7577001d (diff)
downloadlinux-2cc8a6cf8a801065b68550d5af33f62999ce15f0.tar.xz
scsi: mvsas: Don't emit __LINE__ in debug messages
__LINE__ changes quite easily for cleanup commits. So when checking if a cleanup patch introduces changes to the resulting binary each usage of __LINE__ is source of annoyance. So instead of __FILE__ and __LINE__ emit __func__ to give at least some more indication about where the messages originates from than __FILE__ alone; with that and the actual message the situation should be clear enough. While at it reduce duplication by implementing mv_dprintk() using mv_printk(). Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com> Link: https://patch.msgid.link/20260427174545.2014499-2-u.kleine-koenig@baylibre.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
-rw-r--r--drivers/scsi/mvsas/mv_sas.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/drivers/scsi/mvsas/mv_sas.h b/drivers/scsi/mvsas/mv_sas.h
index 09ce3f2241f2..7521f969aa87 100644
--- a/drivers/scsi/mvsas/mv_sas.h
+++ b/drivers/scsi/mvsas/mv_sas.h
@@ -35,10 +35,10 @@
#define MVS_ID_NOT_MAPPED 0x7f
#define WIDE_PORT_MAX_PHY 4
#define mv_printk(fmt, arg ...) \
- printk(KERN_DEBUG"%s %d:" fmt, __FILE__, __LINE__, ## arg)
+ printk(KERN_DEBUG "%s: " fmt, __func__, ## arg)
#ifdef MV_DEBUG
-#define mv_dprintk(format, arg...) \
- printk(KERN_DEBUG"%s %d:" format, __FILE__, __LINE__, ## arg)
+#define mv_dprintk(fmt, arg...) \
+ mv_printk(fmt, ## arg)
#else
#define mv_dprintk(format, arg...) no_printk(format, ## arg)
#endif