[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3e6c21e-8d6e-2665-770c-65f9b98ccf93@iogearbox.net>
Date: Wed, 26 May 2021 08:35:19 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Florent Revest <revest@...omium.org>, bpf@...r.kernel.org
Cc: ast@...nel.org, andrii@...nel.org, kpsingh@...nel.org,
jackmanb@...gle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf v2] libbpf: Move BPF_SEQ_PRINTF and BPF_SNPRINTF to
bpf_helpers.h
On 5/25/21 10:18 PM, Florent Revest wrote:
> These macros are convenient wrappers around the bpf_seq_printf and
> bpf_snprintf helpers. They are currently provided by bpf_tracing.h which
> targets low level tracing primitives. bpf_helpers.h is a better fit.
>
> The __bpf_narg and __bpf_apply macros are needed in both files so
> provided twice and guarded by ifndefs.
>
> Reported-by: Andrii Nakryiko <andrii@...nel.org>
> Signed-off-by: Florent Revest <revest@...omium.org>
Given v1/v2 both target bpf tree in the subject, do you really mean bpf or
rather bpf-next?
Thanks,
Daniel
Powered by blists - more mailing lists