From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Michael Walle <mwalle@kernel.org>,
David Laight <david.laight.linux@gmail.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
Takahiro Kuwano <takahiro.kuwano@infineon.com>,
HyeongJun An <sammiee5311@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: reduce stack usage in spi_nor_parse_sfdp()
Date: Wed, 7 Oct 2026 16:02:02 +0300 [thread overview]
Message-ID: <867bf9d7-f69d-4538-8de7-3a772015b486@linaro.org> (raw)
In-Reply-To: <DLYMG0XY8T4Q.2B4KXOQ9QRM2F@kernel.org>
On 10/7/26 3:57 PM, Michael Walle wrote:
> Hi Arnd,
>
>>>> On Tue Sep 15, 2026 at 9:40 PM CEST, Arnd Bergmann wrote:
>>>>> From: Arnd Bergmann <arnd@arndb.de>
>>>>>
>>>>> Two large spi_nor_flash_parameter structures on a function stack
>>>>> is really too much, and this can exceed an otherwise reasonable
>>>>> frame limit:
>>>>>
>>>>> drivers/mtd/spi-nor/sfdp.c: In function 'spi_nor_parse_sfdp':
>>>>> drivers/mtd/spi-nor/sfdp.c:1717:1: error: the frame size of 1600 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
>
> Will you resend a v2 with Davids proposal? I'd like to get this
> fixed in this cycle. I could also take your patch and add Davids
> proposal on top.
>
Hi, Michael,
Arnd is probably busy at lpc. If no answer from him you can always take
his patch, do the necessary amends and describe them in a [mw: blablah]
section above your S-o-b line.
Cheers,
ta
prev parent reply other threads:[~2026-10-07 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 19:40 Arnd Bergmann
2026-09-15 19:48 ` sashiko-bot
2026-09-16 10:05 ` David Laight
2026-09-21 7:55 ` Michael Walle
2026-09-21 8:59 ` David Laight
2026-09-21 9:24 ` Michael Walle
2026-09-21 10:41 ` David Laight
2026-10-07 12:57 ` Michael Walle
2026-10-07 13:02 ` Tudor Ambarus [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=867bf9d7-f69d-4538-8de7-3a772015b486@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sammiee5311@gmail.com \
--cc=takahiro.kuwano@infineon.com \
--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®