From: Eduard Zingerman <eddyz87@gmail.com>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v5 1/3] selftests/bpf: separate var preset parsing in veristat
Date: Wed, 25 Jun 2025 13:51:09 -0700 [thread overview]
Message-ID: <b30b1790b51fb11afd666d583ce344e450447cb8.camel@gmail.com> (raw)
In-Reply-To: <20250625165904.87820-2-mykyta.yatsenko5@gmail.com>
On Wed, 2025-06-25 at 17:59 +0100, Mykyta Yatsenko wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Refactor var preset parsing in veristat to simplify implementation.
> Prepare parsed variable beforehand so that parsing logic is separated
> from functionality of calculating offsets and searching fields.
> Introduce rvalue struct, storing either int or enum (string value),
> will be reused in the next patch, extract parsing rvalue into a
> separate function.
>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
> ---
This patch is the same as in v4, please don't drop acks.
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
[...]
next prev parent reply other threads:[~2025-06-25 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 16:59 [PATCH bpf-next v5 0/3] Support array presets in veristat Mykyta Yatsenko
2025-06-25 16:59 ` [PATCH bpf-next v5 1/3] selftests/bpf: separate var preset parsing " Mykyta Yatsenko
2025-06-25 20:51 ` Eduard Zingerman [this message]
2025-06-25 16:59 ` [PATCH bpf-next v5 2/3] selftests/bpf: support array presets " Mykyta Yatsenko
2025-06-25 21:46 ` Eduard Zingerman
2025-06-26 17:40 ` Andrii Nakryiko
2025-06-25 16:59 ` [PATCH bpf-next v5 3/3] selftests/bpf: test " Mykyta Yatsenko
2025-06-25 20:57 ` Eduard Zingerman
2025-06-26 18:00 ` [PATCH bpf-next v5 0/3] Support " patchwork-bot+netdevbpf
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=b30b1790b51fb11afd666d583ce344e450447cb8.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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