public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Liam Howlett <liam.howlett@oracle•com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the maple tree
Date: Thu, 17 Feb 2022 19:27:22 +1100	[thread overview]
Message-ID: <20220217192722.1447f4a9@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

Hi all,

After merging the maple tree, today's linux-next build (powerpc
allyesconfig) failed like this:

In file included from /home/sfr/next/next/mm/damon/vaddr.c:762:
/home/sfr/next/next/mm/damon/vaddr-test.h: In function 'damon_test_three_regions_in_vmas':
/home/sfr/next/next/mm/damon/vaddr-test.h:85:1: error: the frame size of 2720 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
   85 | }
      | ^
cc1: all warnings being treated as errors

Caused by commit

  42672fae77a4 ("damon: Convert __damon_va_three_regions to use the VMA iterator")

I have dropped the maple tree for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-02-17  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:27 Stephen Rothwell [this message]
2022-02-18  2:14 ` linux-next: build failure after merge of the maple tree Liam Howlett
  -- strict thread matches above, loose matches on Subject: below --
2022-02-23  0:45 broonie
2022-02-23  2:32 ` Liam Howlett
2022-02-17  8:18 Stephen Rothwell
2022-02-17 19:24 ` Will Deacon
2022-02-18  1:46   ` Liam Howlett

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=20220217192722.1447f4a9@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=liam.howlett@oracle$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=willy@infradead$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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