bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	 kernel-team@fb.com, yonghong.song@linux.dev,
	jose.marchesi@oracle.com,  alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next 0/3] API to access btf_dump emit queue and print single type
Date: Thu, 16 May 2024 17:02:02 -0700	[thread overview]
Message-ID: <15424756c16cb1ace48c1b8de6d99074e31d859c.camel@gmail.com> (raw)
In-Reply-To: <20240516230443.3436233-1-eddyz87@gmail.com>

On Thu, 2024-05-16 at 16:04 -0700, Eduard Zingerman wrote:
> This is a follow-up to the following discussion:
> https://lore.kernel.org/bpf/20240503111836.25275-1-jose.marchesi@oracle.com/
> 
> As suggested by Andrii, this series adds several API functions to
> allow more flexibility with btf dump:
> - a function to add a type and all its dependencies to the emit queue;
> - functions to provide access to the emit queue owned by btf_dump object;
> - a function to print a given type (skipping any dependencies).

The series fails on the CI despite passing local testing,
I'll submit v2 when ready.

[...]

  parent reply	other threads:[~2024-05-17  0:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 23:04 [PATCH bpf-next 0/3] API to access btf_dump emit queue and print single type Eduard Zingerman
2024-05-16 23:04 ` [PATCH bpf-next 1/3] libbpf: put forward declarations to btf_dump->emit_queue Eduard Zingerman
2024-05-16 23:04 ` [PATCH bpf-next 2/3] libbpf: API to access btf_dump emit queue and print single type Eduard Zingerman
2024-05-16 23:04 ` [PATCH bpf-next 3/3] selftests/bpf: tests for btf_dump emit queue API Eduard Zingerman
2024-05-17  0:02 ` Eduard Zingerman [this message]
2024-05-17  2:03   ` [PATCH bpf-next 0/3] API to access btf_dump emit queue and print single type Eduard Zingerman

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=15424756c16cb1ace48c1b8de6d99074e31d859c.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jose.marchesi@oracle.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=yonghong.song@linux.dev \
    /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).