From: Andrii Nakryiko <andriin@fb.com>
To: Song Liu <songliubraving@fb.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"andrii.nakryiko@gmail.com" <andrii.nakryiko@gmail.com>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next] libbpf: dump current version to v0.0.6
Date: Mon, 30 Sep 2019 22:25:50 +0000 [thread overview]
Message-ID: <fb971745-94ac-0cfd-eb5c-ab5128ef943c@fb.com> (raw)
In-Reply-To: <E24A08DB-FAF5-4FB9-BB96-4B76E8CCF807@fb.com>
On 9/30/19 3:22 PM, Song Liu wrote:
>
>
>> On Sep 30, 2019, at 3:16 PM, Andrii Nakryiko <andriin@fb.com> wrote:
>>
>> New release cycle started, let's bump to v0.0.6 proactively.
>
> nit: Typo "dump" in subject.
Doh... because even trivial patches can be screwed up :) Thanks!
Sent v2.
>
> Acked-by: Song Liu <songliubraving@fb.com>
>
>>
>> Signed-off-by: Andrii Nakryiko <andriin@fb.com>
>> ---
>> tools/lib/bpf/libbpf.map | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
>> index d04c7cb623ed..8d10ca03d78d 100644
>> --- a/tools/lib/bpf/libbpf.map
>> +++ b/tools/lib/bpf/libbpf.map
>> @@ -190,3 +190,6 @@ LIBBPF_0.0.5 {
>> global:
>> bpf_btf_get_next_id;
>> } LIBBPF_0.0.4;
>> +
>> +LIBBPF_0.0.6 {
>> +} LIBBPF_0.0.5;
>> --
>> 2.17.1
>>
>
prev parent reply other threads:[~2019-09-30 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 22:16 [PATCH bpf-next] libbpf: dump current version to v0.0.6 Andrii Nakryiko
2019-09-30 22:22 ` Song Liu
2019-09-30 22:25 ` Andrii Nakryiko [this message]
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=fb971745-94ac-0cfd-eb5c-ab5128ef943c@fb.com \
--to=andriin@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@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).