From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: arm allmodconfig
Date: Thu, 9 Apr 2026 00:14:47 +0300 [thread overview]
Message-ID: <adbFR_TmR78DX7mw@ashevche-desk.local> (raw)
In-Reply-To: <ada65r2Poo08mJuc@ashevche-desk.local>
On Wed, Apr 08, 2026 at 11:30:34PM +0300, Andy Shevchenko wrote:
> On Mon, Apr 06, 2026 at 12:13:59PM +0530, Vignesh Raghavendra wrote:
> > On 06/04/26 03:05, Andrew Morton wrote:
> > >
> > > current mm.git, ARCH=arm, gcc-15.2.0
> > >
> > > drivers/mtd/chips/cfi_cmdset_0001.c: In function 'do_write_buffer':
> > > drivers/mtd/chips/cfi_cmdset_0001.c:1883:1: error: the frame size of 1296 bytes is larger than 1280 bytes [-Werror=frame-larger-than=]
> > >
> > > Am I doing something wrong (or unconventional) here?
> > >
> >
> > Thanks for the report. Adding Andy who had attempted to fix this [1]
>
> You meant [2]?
>
> > make allmodconfig ARCH=arm actually sets CONFIG_FRAME_WARN=2048. But, I
> > can see the warning when I change it to 1280 manually (bit strange as I
> > expected 1280 to be default based on definition in lib/Kconfig.debug)
> >
> > I am not seeing any recent code change to this file in at least 6 weeks
> > (the changes are still minor code cleanup and nothing before that for 2
> > years). I can only assume newer gcc is exposing something here?
> >
> > Wondering if you plan to work on your patches further, anytime soon?
>
> Yes, I am about to read again the threads and compare my latest local version
> with that. After additional checks I'll send a v3.
>
> > [1] https://lore.kernel.org/linux-mtd/20260225162406.3815267-1-andriy.shevchenko@linux.intel.com/
>
> [2] https://lore.kernel.org/linux-mtd/20260204012630.2211832-1-andriy.shevchenko@linux.intel.com/
FWIW, v3 just has been sent: 20260408211407.2295175-1-andriy.shevchenko@linux.intel.com
--
With Best Regards,
Andy Shevchenko
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2026-04-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260405143513.268f59ae31ab905630d5fbc8@linux-foundation.org>
2026-04-06 6:43 ` arm allmodconfig Vignesh Raghavendra
2026-04-08 20:30 ` Andy Shevchenko
2026-04-08 21:14 ` Andy Shevchenko [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=adbFR_TmR78DX7mw@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox