From: "Miko Larsson" <mikoxyzzz@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>,
"Miko Larsson via B4 Relay"
<devnull+mikoxyzzz.gmail.com@kernel.org>
Cc: <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 2/3] utest/tracefs-utest: add missing define
Date: Thu, 22 Feb 2024 09:59:17 +0100 [thread overview]
Message-ID: <CZBHFXAPE375.14HREPXS870DV@sakura.myxoz.lan> (raw)
In-Reply-To: <20240221184937.64d71df0@gandalf.local.home>
On Thu Feb 22, 2024 at 12:49 AM CET, Steven Rostedt wrote:
> FTBFS is a rather useless explanation (and I had to even look it up to find
> out what it is ;-)
>
> The change log should show the error and explain why the change fixes the
> problem.
Heh, yeah, you're right. Thanks.
next prev parent reply other threads:[~2024-02-22 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 9:02 [PATCH 0/3] utest: fix FTBFS with clang >=15 Miko Larsson via B4 Relay
2024-02-15 9:02 ` [PATCH 1/3] utest/tracefs-utest: add missing include Miko Larsson via B4 Relay
2024-02-21 23:48 ` Steven Rostedt
2024-02-22 8:57 ` Miko Larsson
2024-02-15 9:02 ` [PATCH 2/3] utest/tracefs-utest: add missing define Miko Larsson via B4 Relay
2024-02-21 23:49 ` Steven Rostedt
2024-02-22 8:59 ` Miko Larsson [this message]
2024-02-15 9:02 ` [PATCH 3/3] utest/trace-utest: add missing include Miko Larsson via B4 Relay
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=CZBHFXAPE375.14HREPXS870DV@sakura.myxoz.lan \
--to=mikoxyzzz@gmail.com \
--cc=devnull+mikoxyzzz.gmail.com@kernel.org \
--cc=linux-trace-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).