linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.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
Date: Mon, 23 Oct 2023 04:32:24 +0100	[thread overview]
Message-ID: <ZTXpSMF8Y1ePP9ba@casper.infradead.org> (raw)
In-Reply-To: <20231023133033.5d54f393@canb.auug.org.au>

On Mon, Oct 23, 2023 at 01:30:33PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> 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,

This would fix it.

diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index 2f1026fba00d..34975532e44c 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -601,7 +601,6 @@ struct seq_buf ppc_hw_desc __initdata = {
 	.buffer = ppc_hw_desc_buf,
 	.size = sizeof(ppc_hw_desc_buf),
 	.len = 0,
-	.readpos = 0,
 };
 
 static __init void probe_machine(void)


Steven, do you prefer fixup patches like this, or do you want a v3 that
includes this?

  reply	other threads:[~2023-10-23  3:32 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  2:30 linux-next: build failure after merge of the ftrace tree Stephen Rothwell
2023-10-23  3:32 ` Matthew Wilcox [this message]
2023-10-23 13:41   ` Steven Rostedt
2023-10-26  1:18 ` Stephen Rothwell
2023-10-26  1:21   ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2025-03-11  5:27 Stephen Rothwell
2025-03-11 13:22 ` Steven Rostedt
2024-11-08  4:21 Stephen Rothwell
2024-11-08 14:59 ` Steven Rostedt
2024-11-08 15:09   ` Alice Ryhl
2024-11-08 20:35     ` Steven Rostedt
2024-11-08 21:05       ` Miguel Ojeda
2024-11-08 21:53         ` Miguel Ojeda
2024-11-09 11:09           ` Steven Rostedt
2024-11-09 11:55             ` Miguel Ojeda
2024-11-09 13:03               ` Steven Rostedt
2024-11-09 16:57                 ` Miguel Ojeda
2024-11-06  3:04 Stephen Rothwell
2024-11-06 15:02 ` Steven Rostedt
2024-11-06 17:47   ` Linus Torvalds
2024-11-20 23:27 ` Stephen Rothwell
2024-10-10  2:46 Stephen Rothwell
2024-10-10  3:13 ` Donglin Peng
2024-10-10 13:27 ` Steven Rostedt
2024-10-10 14:08   ` Donglin Peng
2024-10-10 15:04     ` Steven Rostedt
2024-10-10 15:58     ` Steven Rostedt
2022-01-12  0:31 Stephen Rothwell
2022-01-14  1:02 ` Stephen Rothwell
2022-01-14  1:04   ` Steven Rostedt
2022-01-14  2:16   ` Steven Rostedt
2022-01-14  2:58     ` Stephen Rothwell
2022-01-14  3:02       ` Stephen Rothwell
2022-01-14  3:25         ` Steven Rostedt
2022-01-14  3:34           ` Stephen Rothwell
2022-01-14  3:50             ` Steven Rostedt
2022-01-14  5:12               ` Yinan Liu
2022-01-14  6:42               ` Stephen Rothwell
2021-06-10  8:08 Stephen Rothwell
2021-06-10  8:26 ` Peter Zijlstra
2021-06-10 15:06   ` Steven Rostedt
2021-06-15  6:51     ` Mark-PK Tsai
2020-06-03  7:42 Stephen Rothwell
2020-06-03 15:10 ` Tom Zanussi
2020-06-03 15:22 ` Steven Rostedt
2020-06-03 15:24   ` Tom Zanussi
2020-06-03 15:30     ` Steven Rostedt
2020-06-03 21:49       ` Stephen Rothwell
2014-11-21  7:32 Stephen Rothwell
2014-11-21 10:50 ` Jiri Kosina
2014-11-21 14:20   ` Steven Rostedt
2014-11-21 14:23     ` Jiri Kosina
2014-11-21 14:27     ` Steven Rostedt
2014-11-21 12:43 ` Steven Rostedt
2013-03-01  2:47 Stephen Rothwell
2013-03-01  3:06 ` Steven Rostedt
2013-03-02  2:45 ` Steven Rostedt
2013-03-02  3:42   ` Stephen Rothwell
2013-03-02  3:55     ` Steven Rostedt
2013-03-02  4:17       ` Stephen Rothwell
2013-03-02  4:22         ` Steven Rostedt
2013-03-02  4:55           ` Stephen Rothwell

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=ZTXpSMF8Y1ePP9ba@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.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).