public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: alan.maguire@oracle.com, acme@kernel.org
Cc: ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
	mykolal@fb.com, kernel-team@meta.com, bpf@vger.kernel.org,
	dwarves@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/4] btf_encoder: emit type tags for bpf_arena pointers
Date: Wed, 19 Feb 2025 21:42:00 +0000	[thread overview]
Message-ID: <959439509729b0d29c3ab48997bb8956c329f2e1@linux.dev> (raw)
In-Reply-To: <20250219210520.2245369-1-ihor.solodrai@linux.dev>

On 2/19/25 1:05 PM, Ihor Solodrai wrote:
> This patch series implements emitting appropriate BTF type tags for
> argument and return types of kfuncs marked with KF_ARENA_* flags.

Alan, Arnaldo,

I accidentally put "bpf-next" tag in the subject instead of "dwarves".
Please let me know if I should resend.

> [...]

  parent reply	other threads:[~2025-02-19 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 21:05 [PATCH bpf-next v3 0/4] btf_encoder: emit type tags for bpf_arena pointers Ihor Solodrai
2025-02-19 21:05 ` [PATCH bpf-next v3 1/4] btf_encoder: refactor btf_encoder__tag_kfuncs() Ihor Solodrai
2025-02-19 21:05 ` [PATCH bpf-next v3 2/4] btf_encoder: emit type tags for bpf_arena pointers Ihor Solodrai
2025-02-19 21:05 ` [PATCH bpf-next v3 3/4] pahole: introduce --btf_feature=attributes Ihor Solodrai
2025-02-19 21:05 ` [PATCH bpf-next v3 4/4] man-pages: describe attributes and remove reproducible_build Ihor Solodrai
2025-02-19 21:42 ` Ihor Solodrai [this message]
2025-02-21 11:27   ` [PATCH bpf-next v3 0/4] btf_encoder: emit type tags for bpf_arena pointers Alan Maguire
2025-02-21 14:47 ` Alan Maguire
2025-02-24 20:32   ` Ihor Solodrai
2025-02-25  9:36     ` Alan Maguire

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=959439509729b0d29c3ab48997bb8956c329f2e1@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=mykolal@fb.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