linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: maz@kernel.org, oupton@kernel.org,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	catalin.marinas@arm.com, will@kernel.org, mhiramat@kernel.org,
	alexandru.elisei@arm.com, vdonnefort@google.com,
	joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
	yuzenghui@huawei.com, qperret@google.com, ardb@kernel.org,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	tabba@google.com
Subject: Re: [PATCH v3 01/11] tracing: Include linux/types.h in trace_remote_event.h
Date: Mon, 10 Aug 2026 18:30:17 -0400	[thread overview]
Message-ID: <20260810183017.32db8b80@gandalf.local.home> (raw)
In-Reply-To: <20260804112317.1937387-2-fuad.tabba@linux.dev>

On Tue,  4 Aug 2026 12:23:07 +0100
Fuad Tabba <fuad.tabba@linux.dev> wrote:

> trace_remote_event.h uses bool without including linux/types.h, so a
> translation unit that includes it ahead of anything else that pulls
> types.h in fails to build, as with nvhe/trace.h at EL2.
> 
> Fixes: 072529158e60 ("tracing: Add events to trace remotes")

Is there a config that already fails the build without this change? Or is
it that new code will fail without it?

If it is the former, please drop the fixes tag, as nothing is currently
broken. If it is the latter, then sure, keep it, but you should mention
what config options break with it.

-- Steve


> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
> ---
>  include/linux/trace_remote_event.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/linux/trace_remote_event.h b/include/linux/trace_remote_event.h
> index c8ae1e1f5e721..e4cc2d4497bcf 100644
> --- a/include/linux/trace_remote_event.h
> +++ b/include/linux/trace_remote_event.h
> @@ -3,6 +3,8 @@
>  #ifndef _LINUX_TRACE_REMOTE_EVENTS_H
>  #define _LINUX_TRACE_REMOTE_EVENTS_H
>  
> +#include <linux/types.h>
> +
>  struct trace_remote;
>  struct trace_event_fields;
>  struct trace_seq;



  parent reply	other threads:[~2026-08-10 22:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:23 [PATCH v3 00/11] KVM: arm64: Restore type-checking across the host/hyp hypercall boundary Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 01/11] tracing: Include linux/types.h in trace_remote_event.h Fuad Tabba
2026-08-05 20:54   ` Steven Rostedt
2026-08-06  8:43     ` Fuad Tabba
2026-08-06 12:19       ` Steven Rostedt
2026-08-06 12:35         ` Vincent Donnefort
2026-08-10 22:30   ` Steven Rostedt [this message]
2026-08-04 11:23 ` [PATCH v3 02/11] KVM: arm64: nVHE: Share the stacktrace per-CPU declarations with EL2 Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 03/11] KVM: arm64: nVHE: Declare the hyp event IDs before defining them Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 04/11] KVM: arm64: nVHE: Use NULL to reset the trace buffer backing pointer Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 05/11] KVM: arm64: nVHE: Run the source checker under C=2 Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 06/11] arm64: pi: Run the source checker on the libfdt objects " Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 07/11] KVM: arm64: nVHE: Pass host VA arguments as pointers Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 08/11] KVM: arm64: Move the host hypercall interface to its own header Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 09/11] KVM: arm64: Type-check hypercall arguments at the caller Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 10/11] KVM: arm64: nVHE: Check hypercall handlers against the declared ABI Fuad Tabba
2026-08-04 11:23 ` [PATCH v3 11/11] KVM: arm64: Tag host-VA hypercall parameters __kern Fuad Tabba
2026-08-06  9:17 ` [PATCH v3 00/11] KVM: arm64: Restore type-checking across the host/hyp hypercall boundary Marc Zyngier

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=20260810183017.32db8b80@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=alexandru.elisei@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=fuad.tabba@linux.dev \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=oupton@kernel.org \
    --cc=qperret@google.com \
    --cc=seiden@linux.ibm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.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;
as well as URLs for NNTP newsgroup(s).