From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: yhs@fb.com, ast@kernel.org, olsajiri@gmail.com,
eddyz87@gmail.com, sinquersw@gmail.com, timo@incline.eu,
daniel@iogearbox.net, andrii@kernel.org, songliubraving@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org, sdf@google.com,
haoluo@google.com, martin.lau@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH dwarves] dwarves: sync with libbpf-1.1
Date: Wed, 1 Feb 2023 10:55:44 -0300 [thread overview]
Message-ID: <Y9pvYFPlFEVXJGK1@kernel.org> (raw)
In-Reply-To: <1675169241-32559-1-git-send-email-alan.maguire@oracle.com>
Em Tue, Jan 31, 2023 at 12:47:21PM +0000, Alan Maguire escreveu:
> This will pull in BTF dedup improvements
>
> 082108f libbpf: Resolve unambigous forward declarations
> de048b6 libbpf: Resolve enum fwd as full enum64 and vice versa
> f3c51fe libbpf: Btf dedup identical struct test needs check for nested structs/arrays
So, after running cmake in the build directory to update the libbpf
submodule I'm not finding the above 3 commits:
⬢[acme@toolbox bpf]$ git log --oneline -1
6597330c45d18538 (HEAD, tag: v1.1.0) sync: latest libbpf changes from kernel
⬢[acme@toolbox bpf]$
This matches with the "Subproject commit" below, then:
⬢[acme@toolbox bpf]$ git log --oneline | egrep "Resolve unambigous forward declarations"\|"Resolve enum fwd as full enum64 and vice versa"\|"Btf dedup identical struct test needs check for nested structs/arrays"
758331091179fe47 libbpf: Resolve unambigous forward declarations
3a387f5a8fa8b25f libbpf: Resolve enum fwd as full enum64 and vice versa
6ebbbacb5cb11840 libbpf: Btf dedup identical struct test needs check for nested structs/arrays
⬢[acme@toolbox bpf]$
So I'm updating the commits, ok?
Thanks!
- Arnaldo
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> lib/bpf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/bpf b/lib/bpf
> index 645500d..6597330 160000
> --- a/lib/bpf
> +++ b/lib/bpf
> @@ -1 +1 @@
> -Subproject commit 645500dd7d2d6b5bb76e4c0375d597d4f0c4814e
> +Subproject commit 6597330c45d185381900037f0130712cd326ae59
> --
> 1.8.3.1
next prev parent reply other threads:[~2023-02-01 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 12:47 [PATCH dwarves] dwarves: sync with libbpf-1.1 Alan Maguire
2023-02-01 13:55 ` Arnaldo Carvalho de Melo [this message]
2023-02-01 15:11 ` 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=Y9pvYFPlFEVXJGK1@kernel.org \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@chromium.org \
--cc=martin.lau@kernel.org \
--cc=olsajiri@gmail.com \
--cc=sdf@google.com \
--cc=sinquersw@gmail.com \
--cc=songliubraving@fb.com \
--cc=timo@incline.eu \
--cc=yhs@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