From: Punit Agrawal <punitagrawal@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] tools/bootconfig: Fix a compilation issue with missing variable
Date: Thu, 09 Sep 2021 17:31:04 +0900 [thread overview]
Message-ID: <87a6kmb16f.fsf@stealth> (raw)
In-Reply-To: <20210907204502.26f0e833@rorschach.local.home> (Steven Rostedt's message of "Tue, 7 Sep 2021 20:45:02 -0400")
Hi Steve, Masami,
Steven Rostedt <rostedt@goodmis.org> writes:
> On Wed, 8 Sep 2021 09:41:45 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
>> Hi Steve,
>>
>> I've investigated that why this happens here.
>>
>> https://lore.kernel.org/all/20210831033256.5973-1-jcfaracco@gmail.com/T/#m52f43f6deb874ee726b10ce25ba53e44697a275a
>>
>> This seems a timing issue. I acked a "simplify" patch April, and
>> the I wrongly worked on the linus tree for "mixing a value and subkeys"
>> and send it to you June. At last, those 2 conflicted on your branch and
>> your merge script might just merge it.
>> Actually, what Punit and Julio did is reverting
>>
>> commit 30d103f2d460 ("tools/bootconfig: Simplify expression")
>
> Yep, I came up with the same conclusion ;-)
Thanks for the quick response and looking into the underlying
cause. Looks like it's all sorted now.
If only I could as quickly get to the bottom of the network issue that
triggered this [0]!
Thanks,
Punit
[0] https://lore.kernel.org/all/CAGb2v67Duk_56fOKVwZsYn2HKJ99o8WJ+d4jetD2UjDsAt9BcA@mail.gmail.com/
next prev parent reply other threads:[~2021-09-09 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 23:07 [RESEND PATCH] tools/bootconfig: Fix a compilation issue with missing variable Punit Agrawal
2021-09-08 0:13 ` Masami Hiramatsu
2021-09-08 0:27 ` Steven Rostedt
2021-09-08 0:34 ` Masami Hiramatsu
2021-09-08 0:24 ` Steven Rostedt
2021-09-08 0:41 ` Masami Hiramatsu
2021-09-08 0:45 ` Steven Rostedt
2021-09-09 8:31 ` Punit Agrawal [this message]
2021-09-08 0:44 ` 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=87a6kmb16f.fsf@stealth \
--to=punitagrawal@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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