From: Luben Tuikov <ltuikov89@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Direct Rendering Infrastructure - Development
<dri-devel@lists.freedesktop.org>,
Luben Tuikov <ltuikov89@gmail.com>
Subject: [PATCH] Revert "drm/sched: Define pr_fmt() for DRM using pr_*()"
Date: Fri, 10 Nov 2023 21:41:31 -0500 [thread overview]
Message-ID: <20231111024130.11464-2-ltuikov89@gmail.com> (raw)
This reverts commit 36245bd02e88e68ac5955c2958c968879d7b75a9.
Signed-off-by: Luben Tuikov <ltuikov89@gmail.com>
---
include/drm/drm_print.h | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
index e8fe60d0eb8783..a93a387f8a1a15 100644
--- a/include/drm/drm_print.h
+++ b/include/drm/drm_print.h
@@ -26,20 +26,6 @@
#ifndef DRM_PRINT_H_
#define DRM_PRINT_H_
-/* Define this before including linux/printk.h, so that the format
- * string in pr_*() macros is correctly set for DRM. If a file wants
- * to define this to something else, it should do so before including
- * this header file.
- *
- * It is encouraged code using pr_err() to prefix their format with
- * the string "*ERROR* ", to make it easier to scan kernel logs. For
- * instance,
- * pr_err("*ERROR* <the rest of your format string here>", args).
- */
-#ifndef pr_fmt
-#define pr_fmt(fmt) "[drm] " fmt
-#endif
-
#include <linux/compiler.h>
#include <linux/printk.h>
#include <linux/seq_file.h>
base-commit: 540527b1385fb203cc4513ca838b4de60bbbc49a
--
2.42.1
next reply other threads:[~2023-11-11 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 2:41 Luben Tuikov [this message]
2023-11-11 8:26 ` [PATCH] Revert "drm/sched: Define pr_fmt() for DRM using pr_*()" Javier Martinez Canillas
2023-11-11 8:33 ` Luben Tuikov
2023-11-11 8:56 ` Javier Martinez Canillas
2023-11-11 11:33 ` Jani Nikula
2023-11-14 0:57 ` Luben Tuikov
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=20231111024130.11464-2-ltuikov89@gmail.com \
--to=ltuikov89@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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