From: Jani Nikula <jani.nikula@intel.com>
To: linux-sound@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
jani.nikula@intel.com
Subject: [PATCH] ASoC: hdmi-codec: drop drm/drm_edid.h include
Date: Tue, 12 Dec 2023 16:30:38 +0200 [thread overview]
Message-ID: <20231212143038.3828691-1-jani.nikula@intel.com> (raw)
hdmi-codec.h does not appear to need drm/drm_edid.h for anything. Remove
it.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
I'm pretty sure I haven't compiled everything that might implicitly
depend on the include. However, the right thing to do is to include
drm_edid.h where needed, not from somewhat random intermediate
headers. I hope this uncovers anything I missed.
---
include/sound/hdmi-codec.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/sound/hdmi-codec.h b/include/sound/hdmi-codec.h
index 9b162ac1e08e..5e1a9eafd10f 100644
--- a/include/sound/hdmi-codec.h
+++ b/include/sound/hdmi-codec.h
@@ -12,7 +12,6 @@
#include <linux/of_graph.h>
#include <linux/hdmi.h>
-#include <drm/drm_edid.h>
#include <sound/asoundef.h>
#include <sound/soc.h>
#include <uapi/sound/asound.h>
--
2.39.2
next reply other threads:[~2023-12-12 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:30 Jani Nikula [this message]
2023-12-12 18:53 ` [PATCH] ASoC: hdmi-codec: drop drm/drm_edid.h include kernel test robot
2023-12-13 9:50 ` [PATCH v2] " Jani Nikula
2023-12-13 23:56 ` kernel test robot
2023-12-14 1:56 ` kernel test robot
2023-12-14 6:14 ` kernel test robot
2023-12-14 9:28 ` [PATCH v3] " Jani Nikula
2023-12-14 20:53 ` kernel test robot
2023-12-19 12:12 ` [PATCH v4] " Jani Nikula
2023-12-21 9:35 ` Jani Nikula
2023-12-21 9:48 ` 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=20231212143038.3828691-1-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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