[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20230224160441.98341704b2aee13d6316af12@kernel.org>
Date: Fri, 24 Feb 2023 16:04:41 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Donglin Peng <dolinux.peng@...il.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the ftrace tree
On Fri, 24 Feb 2023 16:34:26 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 2740abcc36cb ("Allow forcing unconditional bootconfig processing")
> d3a1913404bf ("bootconfig: Default BOOT_CONFIG_FORCE to y if BOOT_CONFIG_EMBED")
> 9739868a6e5b ("bootconfig: Increase max nodes of bootconfig from 1024 to 8192 for DCC support")
> 9f58b99c9c40 ("tracing/probe: add a char type to show the character value of traced arguments")
>
> These are commits
>
> b743852ccc1d ("Allow forcing unconditional bootconfig processing")
> 6ded8a28ed80 ("bootconfig: Default BOOT_CONFIG_FORCE to y if BOOT_CONFIG_EMBED")
> 6c40624930c5 ("bootconfig: Increase max nodes of bootconfig from 1024 to 8192 for DCC support")
> 8478cca1e3ab ("tracing/probe: add a char type to show the character value of traced arguments")
Oops, that may be my mistake. I've update bootconfig/for-next which only has the
commits went to the Linus tree. I think linux-trace/for-next is an old set.
Steve, can you update the for-next branch?
Thank you,
>
> in Linus' tree.
>
> --
> Cheers,
> Stephen Rothwell
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists