Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Date:   Wed, 25 Oct 2023 21:21:26 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Masami Hiramatsu <mhiramat@kernel.org>,
        "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: Re: linux-next: build failure after merge of the ftrace tree
Message-ID: <20231025212126.689c6088@gandalf.local.home>
In-Reply-To: <20231026121816.401d2723@canb.auug.org.au>
References: <20231023133033.5d54f393@canb.auug.org.au>
        <20231026121816.401d2723@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 26 Oct 2023 12:18:16 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> On Mon, 23 Oct 2023 13:30:33 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > After merging the ftrace tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > arch/powerpc/kernel/setup-common.c:604:10: error: 'struct seq_buf' has no member named 'readpos'
> >   604 |         .readpos = 0,
> >       |          ^~~~~~~
> > arch/powerpc/kernel/setup-common.c:604:20: error: excess elements in struct initializer [-Werror]
> >   604 |         .readpos = 0,
> >       |                    ^
> > arch/powerpc/kernel/setup-common.c:604:20: note: (near initialization for 'ppc_hw_desc')
> > cc1: all warnings being treated as errors
> > 
> > Caused by commit
> > 
> >   d0ed46b60396 ("tracing: Move readpos from seq_buf to trace_seq")
> > 
> > I have used the ftrace tree from next-20231020 for today.  
> 
> This is still failing ...
> 

Ah, I never pushed it up from trace/for-next to for-next. Thanks for the reminder.

I'll do that now.

-- Steve