From: Marc Zyngier <maz@kernel.org>
To: Vincent Donnefort <vdonnefort@google.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Oliver Upton <oupton@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 1/3] KVM: arm64: fix include path for ring buffer implementation
Date: Thu, 12 Mar 2026 15:45:26 +0000 [thread overview]
Message-ID: <177333027972.824271.5682048908167993643.b4-ty@kernel.org> (raw)
In-Reply-To: <20260312123601.625063-1-arnd@kernel.org>
On Thu, 12 Mar 2026 13:35:42 +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The simple_ring_buffer.c file is in the source tree rather than
> generated at build time, so the include path is wrong when using
> separate object trees:
>
> arch/arm64/kvm/hyp/nvhe/trace.c:16:10: fatal error: simple_ring_buffer.c: No such file or directory
> 16 | #include "simple_ring_buffer.c"
>
> [...]
Applied to next, thanks!
[2/3] tracing: add more symbols to whitelist
commit: 7e4b6c94300e355a72670c5b896ccc26ac312c63
[3/3] KVM: arm64: tracing: add ftrace dependency
commit: 9e5dd49de5d82401e92098c03e0a0e978ddd515a
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-03-12 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 12:35 Arnd Bergmann
2026-03-12 12:35 ` [PATCH 2/3] tracing: add more symbols to whitelist Arnd Bergmann
2026-03-12 13:40 ` Vincent Donnefort
2026-03-12 14:37 ` Arnd Bergmann
2026-03-12 15:21 ` Marc Zyngier
2026-03-12 15:37 ` Arnd Bergmann
2026-03-12 12:35 ` [PATCH 3/3] KVM: arm64: tracing: add ftrace dependency Arnd Bergmann
2026-03-12 13:52 ` Vincent Donnefort
2026-03-12 13:35 ` [PATCH 1/3] KVM: arm64: fix include path for ring buffer implementation Vincent Donnefort
2026-03-12 15:45 ` Marc Zyngier [this message]
2026-03-12 22:08 ` (subset) " Nathan Chancellor
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=177333027972.824271.5682048908167993643.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@kernel.org \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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
all inboxes | Powered by JetHome®