mirror of
https://github.com/torvalds/linux.git
synced 2026-07-27 17:47:41 +02:00
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>
This commit is contained in:
parent
250ba648f4
commit
2cc8a6cf8a
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user