From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH 2/2] drm/print: drop include seq_file.h
Date: Wed, 10 Apr 2024 17:14:34 +0300 [thread overview]
Message-ID: <20240410141434.157908-2-jani.nikula@intel.com> (raw)
In-Reply-To: <20240410141434.157908-1-jani.nikula@intel.com>
Never include where a forward declaration will suffice.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
include/drm/drm_print.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
index 561c3b96b6fd..089950ad8681 100644
--- a/include/drm/drm_print.h
+++ b/include/drm/drm_print.h
@@ -28,7 +28,6 @@
#include <linux/compiler.h>
#include <linux/printk.h>
-#include <linux/seq_file.h>
#include <linux/device.h>
#include <linux/dynamic_debug.h>
@@ -36,6 +35,7 @@
struct debugfs_regset32;
struct drm_device;
+struct seq_file;
/* Do *not* use outside of drm_print.[ch]! */
extern unsigned long __drm_debug;
--
2.39.2
next prev parent reply other threads:[~2024-04-10 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 14:14 [PATCH 1/2] drm/print: drop include debugfs.h and include where needed Jani Nikula
2024-04-10 14:14 ` Jani Nikula [this message]
2024-04-10 14:54 ` Andrzej Hajda
2024-04-10 16:30 ` ✓ CI.Patch_applied: success for series starting with [1/2] " Patchwork
2024-04-10 16:30 ` ✓ CI.checkpatch: " Patchwork
2024-04-10 16:31 ` ✗ CI.KUnit: failure " Patchwork
2024-04-15 13:09 ` [PATCH 1/2] " Jani Nikula
2024-04-15 14:23 ` Maxime Ripard
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=20240410141434.157908-2-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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