From: Jakub Kicinski <jakub.kicinski@netronome•com>
To: Okash Khawaja <osk@fb•com>
Cc: Daniel Borkmann <daniel@iogearbox•net>,
Martin KaFai Lau <kafai@fb•com>,
Alexei Starovoitov <ast@kernel•org>, Yonghong Song <yhs@fb•com>,
Quentin Monnet <quentin.monnet@netronome•com>,
"David S. Miller" <davem@davemloft•net>, <netdev@vger•kernel.org>,
<kernel-team@fb•com>, <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH bpf-next v5 0/3] bpf: btf: print bpftool map data with btf
Date: Wed, 11 Jul 2018 20:30:10 -0700 [thread overview]
Message-ID: <20180711203010.51bab0cf@cakuba.lan> (raw)
In-Reply-To: <20180712030803.875913594@fb.com>
On Wed, 11 Jul 2018 20:08:03 -0700, Okash Khawaja wrote:
> Hi,
>
> Here are the changes from v4:
>
> patch 2:
>
> - sort headers in btf_dumper.c
> - remove extra parentheses
> - include asm/byteorder.h
> - compile error when big and small endian bitfields macro undefined
Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome•com>
Thanks!
next prev parent reply other threads:[~2018-07-12 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 3:08 [PATCH bpf-next v5 0/3] bpf: btf: print bpftool map data with btf Okash Khawaja
2018-07-12 3:08 ` [PATCH bpf-next v5 2/3] bpf: btf: add btf print functionality Okash Khawaja
2018-07-12 3:08 ` [PATCH bpf-next v5 3/3] bpf: btf: print map dump and lookup with btf info Okash Khawaja
2018-07-12 3:30 ` Jakub Kicinski [this message]
2018-07-13 20:49 ` [PATCH bpf-next v5 0/3] bpf: btf: print bpftool map data with btf Daniel Borkmann
2018-07-13 21:35 ` Okash Khawaja
2018-07-13 22:35 ` Daniel Borkmann
2018-07-13 22:43 ` Okash Khawaja
-- strict thread matches above, loose matches on Subject: below --
2018-07-14 4:57 Okash Khawaja
2018-07-14 11:03 ` Daniel Borkmann
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=20180711203010.51bab0cf@cakuba.lan \
--to=jakub.kicinski@netronome$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=kafai@fb$(echo .)com \
--cc=kernel-team@fb$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=osk@fb$(echo .)com \
--cc=quentin.monnet@netronome$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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