From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: realtek: add missing MODULE_DEVICE_TABLE()
Date: Mon, 06 Jul 2026 16:09:15 +0200 [thread overview]
Message-ID: <87tsqcky5w.fsf@bootlin.com> (raw)
In-Reply-To: <20260704123044.31740-1-pengpeng@iscas.ac.cn> (Pengpeng Hou's message of "Sat, 4 Jul 2026 20:30:44 +0800")
Hi Pengpeng,
On 04/07/2026 at 20:30:44 +08, Pengpeng Hou <pengpeng@iscas.ac.cn> wrote:
> The driver has an OF match table wired to .of_match_table, but does
> not export the table with MODULE_DEVICE_TABLE().
>
> Add the missing MODULE_DEVICE_TABLE(of, ...) entry so module alias
> information is generated for OF based module autoloading.
>
> This is a source-level fix. It does not claim dynamic hardware
> reproduction; the evidence is the driver-owned match table, its use by
> the platform driver, and the missing module alias publication.
Why do you never add any Fixes and Cc stable tags? This is a behavioural
fix, which probably deserves to be backported. It is the third or even
maybe fourth time that I have to ask for those tags within 2
weeks. Please consider adding them proactively when relevant.
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: realtek: add missing MODULE_DEVICE_TABLE()
Date: Mon, 06 Jul 2026 16:09:15 +0200 [thread overview]
Message-ID: <87tsqcky5w.fsf@bootlin.com> (raw)
In-Reply-To: <20260704123044.31740-1-pengpeng@iscas.ac.cn> (Pengpeng Hou's message of "Sat, 4 Jul 2026 20:30:44 +0800")
Hi Pengpeng,
On 04/07/2026 at 20:30:44 +08, Pengpeng Hou <pengpeng@iscas.ac.cn> wrote:
> The driver has an OF match table wired to .of_match_table, but does
> not export the table with MODULE_DEVICE_TABLE().
>
> Add the missing MODULE_DEVICE_TABLE(of, ...) entry so module alias
> information is generated for OF based module autoloading.
>
> This is a source-level fix. It does not claim dynamic hardware
> reproduction; the evidence is the driver-owned match table, its use by
> the platform driver, and the missing module alias publication.
Why do you never add any Fixes and Cc stable tags? This is a behavioural
fix, which probably deserves to be backported. It is the third or even
maybe fourth time that I have to ask for those tags within 2
weeks. Please consider adding them proactively when relevant.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-07-06 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 12:30 [PATCH] mtd: rawnand: realtek: add missing MODULE_DEVICE_TABLE() Pengpeng Hou
2026-07-04 12:30 ` Pengpeng Hou
2026-07-06 14:09 ` Miquel Raynal [this message]
2026-07-06 14:09 ` 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=87tsqcky5w.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pengpeng@iscas.ac.cn \
--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.