From: Thomas Zimmermann <tzimmermann@suse.de>
To: ysato@users.sourceforge.jp, dalias@libc.org,
glaubitz@physik.fu-berlin.de, lee@kernel.org, danielt@kernel.org,
simona.vetter@ffwll.ch
Cc: linux-sh@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
kernel test robot <lkp@intel.com>,
Jingoo Han <jingoohan1@gmail.com>
Subject: [PATCH] arch: sh: Include <linux/io.h> in dac.h
Date: Tue, 28 Oct 2025 18:07:55 +0100 [thread overview]
Message-ID: <20251028170913.16711-1-tzimmermann@suse.de> (raw)
Include <linux/io.h> to avoid depending on <linux/backlight.h> for
including it. Declares __raw_readb() and __raw_writeb().
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202510282206.wI0HrqcK-lkp@intel.com/
Fixes: 243ce64b2b37 ("backlight: Do not include <linux/fb.h> in header file")
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Daniel Thompson (RISCstar) <danielt@kernel.org>
Cc: Simona Vetter <simona.vetter@ffwll.ch>
Cc: Lee Jones <lee@kernel.org>
Cc: Daniel Thompson <danielt@kernel.org>
Cc: Jingoo Han <jingoohan1@gmail.com>
Cc: dri-devel@lists.freedesktop.org
---
This is fallout from a recent cleanup of the backlight header file. I don't
have the option of building or testing this change, though.
---
arch/sh/include/cpu-sh3/cpu/dac.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/sh/include/cpu-sh3/cpu/dac.h b/arch/sh/include/cpu-sh3/cpu/dac.h
index fd02331608a8..323ec8570bcd 100644
--- a/arch/sh/include/cpu-sh3/cpu/dac.h
+++ b/arch/sh/include/cpu-sh3/cpu/dac.h
@@ -2,6 +2,8 @@
#ifndef __ASM_CPU_SH3_DAC_H
#define __ASM_CPU_SH3_DAC_H
+#include <linux/io.h>
+
/*
* Copyright (C) 2003 Andriy Skulysh
*/
--
2.51.1
next reply other threads:[~2025-10-28 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:07 Thomas Zimmermann [this message]
2025-10-28 17:12 ` [PATCH] arch: sh: Include <linux/io.h> in dac.h John Paul Adrian Glaubitz
2025-10-30 11:20 ` Daniel Thompson
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=20251028170913.16711-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=dalias@libc.org \
--cc=danielt@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jingoohan1@gmail.com \
--cc=lee@kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkp@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).