From: Paz Zcharya <pazz@chromium.org>
To: "Jouni Högander" <jouni.hogander@intel.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Luca Coelho" <luciano.coelho@intel.com>
Cc: Subrata Banik <subratabanik@google.com>,
Manasi Navare <navaremanasi@chromium.org>,
Drew Davenport <ddavenport@chromium.org>,
Sean Paul <seanpaul@chromium.org>,
Marcin Wojtas <mwojtas@chromium.org>,
khaled.almahallawy@intel.com, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Paz Zcharya <pazz@chromium.org>
Subject: [PATCH] drm/i915/display: Include debugfs.h in intel_display_debugfs_params.c
Date: Wed, 31 Jan 2024 20:46:54 +0000 [thread overview]
Message-ID: <20240131204658.795278-1-pazz@chromium.org> (raw)
Commit 8015bee0bfec ("drm/i915/display: Add framework to add parameters
specific to display") added the file intel_display_debugfs_params.c,
which calls the functions "debugfs_create_{bool, ulong, str}" -- all of
which are defined in <linux/debugfs.h>. The missing inclusion of this
header file is breaking the ChromeOS build -- add an explicit include
to fix that.
Signed-off-by: Paz Zcharya <pazz@chromium.org>
---
drivers/gpu/drm/i915/display/intel_display_debugfs_params.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs_params.c b/drivers/gpu/drm/i915/display/intel_display_debugfs_params.c
index b7e68eb62452..f35718748555 100644
--- a/drivers/gpu/drm/i915/display/intel_display_debugfs_params.c
+++ b/drivers/gpu/drm/i915/display/intel_display_debugfs_params.c
@@ -3,6 +3,7 @@
* Copyright © 2023 Intel Corporation
*/
+#include <linux/debugfs.h>
#include <linux/kernel.h>
#include <drm/drm_drv.h>
--
2.43.0.594.gd9cf4e227d-goog
next reply other threads:[~2024-01-31 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 20:46 Paz Zcharya [this message]
2024-02-01 9:22 ` Jani Nikula
2024-02-01 14:58 ` Paz Zcharya
2024-02-01 15:16 ` Jani Nikula
2024-02-02 9:35 ` Jani Nikula
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=20240131204658.795278-1-pazz@chromium.org \
--to=pazz@chromium.org \
--cc=ddavenport@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@intel.com \
--cc=khaled.almahallawy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=mwojtas@chromium.org \
--cc=navaremanasi@chromium.org \
--cc=seanpaul@chromium.org \
--cc=subratabanik@google.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
all inboxes | Powered by JetHome®