SUPERH platform development
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Florian Fuchs <fuchsfl@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 linux-mtd@lists.infradead.org, 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>,
	 Artur Rojek <contact@artur-rojek.eu>
Subject: Re: [PATCH v3 0/3] mtd: maps: vmu-flash: Fix build and runtime errors
Date: Mon, 18 May 2026 14:06:08 +0200	[thread overview]
Message-ID: <87fr3oudlb.fsf@bootlin.com> (raw)
In-Reply-To: <20260518114521.81564-1-fuchsfl@gmail.com> (Florian Fuchs's message of "Mon, 18 May 2026 13:45:18 +0200")

Hi Florian,

On 18/05/2026 at 13:45:18 +02, Florian Fuchs <fuchsfl@gmail.com> wrote:

> Hi all,
>
> This small series fixes build and runtime errors in the vmu-flash driver
> (enabled by CONFIG_MTD_VMU) and the related 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 mtdinfo 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
> ---

I believe there is no issue in applying patches 2 and 3 on top of the
mtd tree and let whoever is responsible take patch 1. If I get an ack I
can also carry patch 1 through the mtd tree. Without more feedback I
plan on applying patches 2 and 3 in the coming weeks.

Thanks,
Miquèl

      parent reply	other threads:[~2026-05-18 12:06 UTC|newest]

Thread overview: 5+ 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 ` [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 ` [PATCH v3 3/3] mtd: maps: vmu-flash: fix NULL pointer dereference in initialization Florian Fuchs
2026-05-18 12:06 ` Miquel Raynal [this message]

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=87fr3oudlb.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=adrian@newgolddream.dyndns.info \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=fuchsfl@gmail.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox