From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Donglin Peng <dolinux.peng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the ftrace tree
Date: Fri, 24 Feb 2023 16:04:41 +0900 [thread overview]
Message-ID: <20230224160441.98341704b2aee13d6316af12@kernel.org> (raw)
In-Reply-To: <20230224163426.7e4d956b@canb.auug.org.au>
On Fri, 24 Feb 2023 16:34:26 +1100
Stephen Rothwell <sfr@canb.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@kernel.org>
next prev parent reply other threads:[~2023-02-24 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 5:34 linux-next: duplicate patches in the ftrace tree Stephen Rothwell
2023-02-24 7:04 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 4:51 Stephen Rothwell
2023-04-03 20:08 ` Ross Zwisler
2023-07-14 4:54 Stephen Rothwell
2023-07-14 8:31 ` Masami Hiramatsu
2024-09-26 21:54 Stephen Rothwell
2024-09-27 16:59 ` Steven Rostedt
2025-03-31 22:40 Stephen Rothwell
2025-03-31 23:45 ` Steven Rostedt
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=20230224160441.98341704b2aee13d6316af12@kernel.org \
--to=mhiramat@kernel.org \
--cc=dolinux.peng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@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