linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Anton Altaparmakov <anton@tuxera.com>,
	Joel Stanley <joel@jms.id.au>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build failure after merge of almost all the trees
Date: Wed, 3 Nov 2021 15:47:53 +1100	[thread overview]
Message-ID: <20211103154753.115d243f@canb.auug.org.au> (raw)
In-Reply-To: <20211028212651.57beb05b@canb.auug.org.au>

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

Hi all,

On Thu, 28 Oct 2021 21:26:51 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> Today's linux-next build (powerpc allyesconfig) failed like this:
> 
> fs/ntfs/aops.c: In function 'ntfs_write_mst_block':
> fs/ntfs/aops.c:1311:1: error: the frame size of 2304 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
>  1311 | }
>       | ^
> cc1: all warnings being treated as errors
> 
> I have no idea what has caused this.
> 
> I have disabled ntfs for now.

So from today, I have used this instead (i.e. disable CONFIG_NTFS_RW):

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 3 Nov 2021 15:17:17 +1100
Subject: [PATCH] Mark NTFS_RW as BROKEN

it currently breaks the ppc allyesonfig build

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 fs/ntfs/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/ntfs/Kconfig b/fs/ntfs/Kconfig
index 1667a7e590d8..68cfef0280f2 100644
--- a/fs/ntfs/Kconfig
+++ b/fs/ntfs/Kconfig
@@ -52,6 +52,7 @@ config NTFS_DEBUG
 config NTFS_RW
 	bool "NTFS write support"
 	depends on NTFS_FS
+	depends on BROKEN
 	help
 	  This enables the partial, but safe, write support in the NTFS driver.
 
-- 
2.33.0

-- 
Cheers,
Stephen Rothwell

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

      parent reply	other threads:[~2021-11-03  4:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 10:26 linux-next: build failure after merge of almost all the trees Stephen Rothwell
2021-10-28 12:38 ` Stephen Rothwell
2021-11-02  6:44   ` Stephen Rothwell
2021-11-02  7:06     ` Arnd Bergmann
2021-11-02 12:13       ` Stephen Rothwell
2021-11-02 12:19         ` Stephen Rothwell
2021-11-02 13:11           ` Arnd Bergmann
2021-11-03  4:47 ` Stephen Rothwell [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=20211103154753.115d243f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=anton@tuxera.com \
    --cc=arnd@arndb.de \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).