From: Florian Fuchs <fuchsfl@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Rich Felker <dalias@libc.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Adrian McMenamin <adrian@newgolddream.dyndns.info>,
Florian Fuchs <fuchsfl@gmail.com>,
Artur Rojek <contact@artur-rojek.eu>
Subject: [PATCH v3 1/3] maple: fix build error due to missing include of linux/device.h
Date: Mon, 18 May 2026 13:45:19 +0200 [thread overview]
Message-ID: <20260518114521.81564-2-fuchsfl@gmail.com> (raw)
In-Reply-To: <20260518114521.81564-1-fuchsfl@gmail.com>
The commit 313162d0b838 ("device.h: audit and cleanup users in main
include dir") removed the include linux/device.h from linux/maple.h,
which led to build errors as linux/maple.h embeds struct device via
struct maple_device. So restore this, as it otherwise results in errors:
./include/linux/maple.h:81:16: error: field 'dev' has incomplete type
struct device dev;
Fixes: 313162d0b838 ("device.h: audit and cleanup users in main include dir")
Cc: stable@vger.kernel.org
Signed-off-by: Florian Fuchs <fuchsfl@gmail.com>
---
v2->v3: no functional change, reword commit message, align subject to
main includedir, add Cc tag
v1->v2: no functional change, just rebase patch
v2: https://lore.kernel.org/lkml/20260427114750.2480900-2-fuchsfl@gmail.com/
v1: https://lore.kernel.org/lkml/20251117224408.498449-2-fuchsfl@gmail.com/
include/linux/maple.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/maple.h b/include/linux/maple.h
index 3be4e567473c..22f2930251ed 100644
--- a/include/linux/maple.h
+++ b/include/linux/maple.h
@@ -2,10 +2,9 @@
#ifndef __LINUX_MAPLE_H
#define __LINUX_MAPLE_H
+#include <linux/device.h>
#include <mach/maple.h>
-struct device;
-
/* Maple Bus command and response codes */
enum maple_code {
MAPLE_RESPONSE_FILEERR = -5,
--
2.43.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fuchs <fuchsfl@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Rich Felker <dalias@libc.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Adrian McMenamin <adrian@newgolddream.dyndns.info>,
Florian Fuchs <fuchsfl@gmail.com>,
Artur Rojek <contact@artur-rojek.eu>
Subject: [PATCH v3 1/3] maple: fix build error due to missing include of linux/device.h
Date: Mon, 18 May 2026 13:45:19 +0200 [thread overview]
Message-ID: <20260518114521.81564-2-fuchsfl@gmail.com> (raw)
In-Reply-To: <20260518114521.81564-1-fuchsfl@gmail.com>
The commit 313162d0b838 ("device.h: audit and cleanup users in main
include dir") removed the include linux/device.h from linux/maple.h,
which led to build errors as linux/maple.h embeds struct device via
struct maple_device. So restore this, as it otherwise results in errors:
./include/linux/maple.h:81:16: error: field 'dev' has incomplete type
struct device dev;
Fixes: 313162d0b838 ("device.h: audit and cleanup users in main include dir")
Cc: stable@vger.kernel.org
Signed-off-by: Florian Fuchs <fuchsfl@gmail.com>
---
v2->v3: no functional change, reword commit message, align subject to
main includedir, add Cc tag
v1->v2: no functional change, just rebase patch
v2: https://lore.kernel.org/lkml/20260427114750.2480900-2-fuchsfl@gmail.com/
v1: https://lore.kernel.org/lkml/20251117224408.498449-2-fuchsfl@gmail.com/
include/linux/maple.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/maple.h b/include/linux/maple.h
index 3be4e567473c..22f2930251ed 100644
--- a/include/linux/maple.h
+++ b/include/linux/maple.h
@@ -2,10 +2,9 @@
#ifndef __LINUX_MAPLE_H
#define __LINUX_MAPLE_H
+#include <linux/device.h>
#include <mach/maple.h>
-struct device;
-
/* Maple Bus command and response codes */
enum maple_code {
MAPLE_RESPONSE_FILEERR = -5,
--
2.43.0
next prev parent reply other threads:[~2026-05-18 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:45 [PATCH v3 0/3] mtd: maps: vmu-flash: Fix build and runtime errors Florian Fuchs
2026-05-18 11:45 ` Florian Fuchs
2026-05-18 11:45 ` Florian Fuchs [this message]
2026-05-18 11:45 ` [PATCH v3 1/3] maple: fix build error due to missing include of linux/device.h Florian Fuchs
2026-05-18 11:45 ` [PATCH v3 2/3] mtd: maps: vmu-flash: fix fault in unaligned fixup Florian Fuchs
2026-05-18 11:45 ` Florian Fuchs
2026-05-18 11:45 ` [PATCH v3 3/3] mtd: maps: vmu-flash: fix NULL pointer dereference in initialization Florian Fuchs
2026-05-18 11:45 ` Florian Fuchs
2026-05-18 12:06 ` [PATCH v3 0/3] mtd: maps: vmu-flash: Fix build and runtime errors Miquel Raynal
2026-05-18 12:06 ` Miquel Raynal
2026-05-27 9:08 ` Miquel Raynal
2026-05-27 9:08 ` Miquel Raynal
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=20260518114521.81564-2-fuchsfl@gmail.com \
--to=fuchsfl@gmail.com \
--cc=adrian@newgolddream.dyndns.info \
--cc=contact@artur-rojek.eu \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.