From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] tracing/boot: bootconfig: Fixes and API name change
Date: Thu, 9 Sep 2021 22:26:28 +0900 [thread overview]
Message-ID: <20210909222628.7bd301e0179b9dd4b1c9170f@kernel.org> (raw)
In-Reply-To: <20210909091123.29f17a6f@gandalf.local.home>
On Thu, 9 Sep 2021 09:11:23 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 9 Sep 2021 21:48:43 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Hi,
> >
> > Here is a series of patches to fix some issues on boot-time tracing
> > and bootconfig. Yesterday I sent a bugfix(*), and today I found some
> > other issues.
> >
> > (*) https://lore.kernel.org/all/163112988361.74896.2267026262061819145.stgit@devnote2/T/#u
> >
> > This includes following patches.
> >
> > [1/3] tracing/boot: Fix trace_boot_hist_add_array() to check array is value
> >
> > [2/3] tracing/boot: Fix to check the histogram control param is a leaf node
> >
> > [3/3] bootconfig: Rename xbc_node_find_child() to xbc_node_find_subkey()
> > - Rename xbc_node_find_child() to xbc_node_find_subkey() to avoid
> > confusing "child" and "subkey" words.
> >
>
> Masami,
>
> Did this go out correctly?
>
> I only received this email, and this email is not showing up on LKML.
>
> (https://lore.kernel.org/r/163119172318.151131.7138254940364392100.stgit%40devnote2
> gives "Not found")
Oops, please ignore this. Maybe something went wrong.
Hmm, OK, let me resend it with [RESEND] tag.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-09-09 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 12:48 [PATCH 0/3] tracing/boot: bootconfig: Fixes and API name change Masami Hiramatsu
2021-09-09 13:11 ` Steven Rostedt
2021-09-09 13:26 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-09 13:12 Masami Hiramatsu
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=20210909222628.7bd301e0179b9dd4b1c9170f@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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