From: "Arnd Bergmann" <arnd@arndb.de>
To: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] mtd: dc21285: fix bytewise memcpy()
Date: Thu, 07 Aug 2025 13:55:08 +0200 [thread overview]
Message-ID: <bb5c1c40-874a-4b30-b606-1785f00e9be9@app.fastmail.com> (raw)
In-Reply-To: <87o6srd0sh.fsf@bootlin.com>
On Thu, Aug 7, 2025, at 09:54, Miquel Raynal wrote:
>
> On 07/08/2025 at 09:20:34 +02, Arnd Bergmann <arnd@kernel.org> wrote:
>
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> The commit that split up the 8/16/32-bit operations in 2004 seems to have
>> broken the 8-bit case, as clang-21 now points out:
>>
>> drivers/mtd/maps/dc21285.c:129:97: error: parameter 'len' set but not used [-Werror,-Wunused-but-set-parameter]
>> 129 | static void dc21285_copy_to_8(struct map_info *map, unsigned long to, const void *from, ssize_t len)
>>
>> Put back the loop that was in linux-2.6.8 and earlier for this case.
>>
>> Fixes: 67d4878e4e61 ("NOR flash drivers update")
>> Cc: David Woodhouse <dwmw2@infradead.org>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Thanks for the patch, I'll take it, but that probably means few to no
> people still use it, if broken for more than 20 years...
Yes, certainly. I also have a patch to mark the mach-footbridge
platform as deprecated and schedule it for removal, I need to
resend that patch.
What I suspect happened here is that the bug was harmless
because the few boards that use this driver all have
16-bit or 32-bit flashes, while the 8-bit codepath was indeed
unused.
Arnd
prev parent reply other threads:[~2025-08-07 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:20 Arnd Bergmann
2025-08-07 7:54 ` Miquel Raynal
2025-08-07 11:55 ` Arnd Bergmann [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=bb5c1c40-874a-4b30-b606-1785f00e9be9@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dwmw2@infradead.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=miquel.raynal@bootlin.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®