From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: sdf@google.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf 0/2] libbpf fix up and clarify version info
Date: Sat, 23 Mar 2019 00:47:53 +0100 [thread overview]
Message-ID: <20190322234755.29306-1-daniel@iogearbox.net> (raw)
First one is fixing version in Makefile and shared object and
second one clarifies bump in version. Thanks!
Daniel Borkmann (2):
bpf, libbpf: fix version info and add it to shared object
bpf, libbpf: clarify bump in libbpf version info
tools/lib/bpf/Makefile | 42 ++++++++++++++++++++++++++++--------------
tools/lib/bpf/README.rst | 1 +
2 files changed, 29 insertions(+), 14 deletions(-)
--
2.9.5
next reply other threads:[~2019-03-22 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 23:47 Daniel Borkmann [this message]
2019-03-22 23:47 ` [PATCH bpf 1/2] bpf, libbpf: fix version info and add it to shared object Daniel Borkmann
2019-03-23 0:09 ` Stanislav Fomichev
2019-03-23 0:19 ` Daniel Borkmann
2019-03-23 0:28 ` Stanislav Fomichev
2019-03-23 0:38 ` Daniel Borkmann
2019-03-22 23:47 ` [PATCH bpf 2/2] bpf, libbpf: clarify bump in libbpf version info 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=20190322234755.29306-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.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