From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org,
Julius Werner <jwerner@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bootconfig: Fix to terminate value search if it hits a newline
Date: Fri, 30 Jan 2026 09:53:31 -0500 [thread overview]
Message-ID: <20260130095331.5c9f754e@gandalf.local.home> (raw)
In-Reply-To: <176974810577.124104.16012554973099890517.stgit@devnote2>
On Fri, 30 Jan 2026 13:41:45 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> Note that if the line has a comment, it still keep searching the
> value to the next line::
>
> foo = # comment
> value
Hmm, so the above is the same as: foo = "value";
But what is:
foo = value # comment
bar
?
Would that be foo = value bar;
Or simply an error. Or would both be an error?
OK, this isn't related to the patch, but as comment processing was brought
to my attention, I'm wondering how it works for the above.
>
> This is interpreted as `foo = "value"`.
> This also updates the test script so that it can check the above cases.
>
> Fixes: 76db5a27a827 ("bootconfig: Add Extra Boot Config support")
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> tools/bootconfig/test-bootconfig.sh | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
As for the patch itself:
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2026-01-30 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 4:41 [PATCH] bootconfig: Fix to terminate value search if it hits a newline Masami Hiramatsu (Google)
2026-01-30 14:53 ` Steven Rostedt [this message]
2026-01-30 23:26 ` Julius Werner
2026-01-31 2:19 ` Masami Hiramatsu
2026-02-02 23:05 ` Julius Werner
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=20260130095331.5c9f754e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jwerner@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.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