All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Florian Fuchs <fuchsfl@gmail.com>
Subject: [PATCH 0/3] mtd: maps: vmu-flash: Fix build and runtime errors
Date: Mon, 17 Nov 2025 23:44:05 +0100	[thread overview]
Message-ID: <20251117224408.498449-1-fuchsfl@gmail.com> (raw)

Hi all,

This small series fixes build and runtime errors in the vmu-flash driver
(enabled by CONFIG_MTD_VMU) and the included maple.h. These changes were
verified on real Dreamcast hardware with a physical VMU. The VMU can now
be successfully probed, read and written with MTD tools like mtd_info and
mtd_debug. Previously, the driver failed to build or crashed during
probing.

	bash-5.3# mtdinfo /dev/mtd0
	mtd0
	Name:                           vmu2.1.0
	Type:                           mlc-nand
	Eraseblock size:                512 bytes
	Amount of eraseblocks:          256 (131072 bytes, 128.0 KiB)
	Minimum input/output unit size: 512 bytes
	Sub-page size:                  512 bytes
	Character device major/minor:   90:0
	Bad blocks are allowed:         true
	Device is writable:             true

Thanks,
Florian

Florian Fuchs (3):
  sh: maple: Fix build error due to missing include of linux/device.h
  mtd: maps: vmu-flash: Fix fault in unaligned fixup
  mtd: maps: vmu-flash: Fix NULL pointer dereference in initialization

 drivers/mtd/maps/vmu-flash.c | 8 +++++---
 include/linux/maple.h        | 2 --
 2 files changed, 5 insertions(+), 5 deletions(-)


base-commit: 97315e7c901a1de60e8ca9b11e0e96d0f9253e18
-- 
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>,
	Florian Fuchs <fuchsfl@gmail.com>
Subject: [PATCH 0/3] mtd: maps: vmu-flash: Fix build and runtime errors
Date: Mon, 17 Nov 2025 23:44:05 +0100	[thread overview]
Message-ID: <20251117224408.498449-1-fuchsfl@gmail.com> (raw)

Hi all,

This small series fixes build and runtime errors in the vmu-flash driver
(enabled by CONFIG_MTD_VMU) and the included maple.h. These changes were
verified on real Dreamcast hardware with a physical VMU. The VMU can now
be successfully probed, read and written with MTD tools like mtd_info and
mtd_debug. Previously, the driver failed to build or crashed during
probing.

	bash-5.3# mtdinfo /dev/mtd0
	mtd0
	Name:                           vmu2.1.0
	Type:                           mlc-nand
	Eraseblock size:                512 bytes
	Amount of eraseblocks:          256 (131072 bytes, 128.0 KiB)
	Minimum input/output unit size: 512 bytes
	Sub-page size:                  512 bytes
	Character device major/minor:   90:0
	Bad blocks are allowed:         true
	Device is writable:             true

Thanks,
Florian

Florian Fuchs (3):
  sh: maple: Fix build error due to missing include of linux/device.h
  mtd: maps: vmu-flash: Fix fault in unaligned fixup
  mtd: maps: vmu-flash: Fix NULL pointer dereference in initialization

 drivers/mtd/maps/vmu-flash.c | 8 +++++---
 include/linux/maple.h        | 2 --
 2 files changed, 5 insertions(+), 5 deletions(-)


base-commit: 97315e7c901a1de60e8ca9b11e0e96d0f9253e18
-- 
2.43.0


             reply	other threads:[~2025-11-17 22:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 22:44 Florian Fuchs [this message]
2025-11-17 22:44 ` [PATCH 0/3] mtd: maps: vmu-flash: Fix build and runtime errors Florian Fuchs
2025-11-17 22:44 ` [PATCH 1/3] sh: maple: Fix build error due to missing include of linux/device.h Florian Fuchs
2025-11-17 22:44   ` Florian Fuchs
2025-11-17 22:44 ` [PATCH 2/3] mtd: maps: vmu-flash: Fix fault in unaligned fixup Florian Fuchs
2025-11-17 22:44   ` Florian Fuchs
2025-11-17 22:44 ` [PATCH 3/3] mtd: maps: vmu-flash: Fix NULL pointer dereference in initialization Florian Fuchs
2025-11-17 22:44   ` Florian Fuchs
2025-11-18  7:31 ` [PATCH 0/3] mtd: maps: vmu-flash: Fix build and runtime errors John Paul Adrian Glaubitz
2025-11-18  7:31   ` John Paul Adrian Glaubitz
2025-11-19 21:36   ` Artur Rojek
2025-11-19 21:36     ` Artur Rojek
2025-11-19 21:44     ` Florian Fuchs
2025-11-19 21:44       ` Florian Fuchs
2025-11-19 21:54       ` Artur Rojek
2025-11-19 21:54         ` Artur Rojek
2025-11-20  8:52         ` Florian Fuchs
2025-11-20  8:52           ` Florian Fuchs
2025-11-20  9:09           ` John Paul Adrian Glaubitz
2025-11-20  9:09             ` John Paul Adrian Glaubitz

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=20251117224408.498449-1-fuchsfl@gmail.com \
    --to=fuchsfl@gmail.com \
    --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.