bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: dwarves@vger.kernel.org, acme@kernel.org, bpf@vger.kernel.org,
	kernel-team@fb.com, Hao Luo <haoluo@google.com>
Subject: Re: [PATCH dwarves 0/2] Fix pahole to emit kernel module BTF variables
Date: Sun, 13 Dec 2020 21:27:57 +0100	[thread overview]
Message-ID: <20201213202757.GA482741@krava> (raw)
In-Reply-To: <20201211041139.589692-1-andrii@kernel.org>

On Thu, Dec 10, 2020 at 08:11:36PM -0800, Andrii Nakryiko wrote:
> Two bug fixes to make pahole emit correct kernel module BTF variable
> information.
> 
> Cc: Hao Luo <haoluo@google.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> 
> Andrii Nakryiko (2):
>   btf_encoder: fix BTF variable generation for kernel modules
>   btf_encoder: fix skipping per-CPU variables at offset 0

Acked-by: Jiri Olsa <jolsa@redhat.com>

jirka

> 
>  btf_encoder.c | 61 +++++++++++++++++++++++++++++++++------------------
>  libbtf.c      |  1 +
>  libbtf.h      |  1 +
>  3 files changed, 42 insertions(+), 21 deletions(-)
> 
> -- 
> 2.24.1
> 


  parent reply	other threads:[~2020-12-13 20:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  4:11 [PATCH dwarves 0/2] Fix pahole to emit kernel module BTF variables Andrii Nakryiko
2020-12-11  4:11 ` [PATCH dwarves 1/2] btf_encoder: fix BTF variable generation for kernel modules Andrii Nakryiko
2020-12-11  4:11 ` [PATCH dwarves 2/2] btf_encoder: fix skipping per-CPU variables at offset 0 Andrii Nakryiko
2020-12-15  0:50   ` Hao Luo
2020-12-13 20:27 ` Jiri Olsa [this message]
2020-12-14 13:43   ` [PATCH dwarves 0/2] Fix pahole to emit kernel module BTF variables Arnaldo Carvalho de Melo
2020-12-15  1:28     ` Andrii Nakryiko
2020-12-15 13:28       ` Arnaldo Carvalho de Melo

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=20201213202757.GA482741@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=haoluo@google.com \
    --cc=kernel-team@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;
as well as URLs for NNTP newsgroup(s).