All of lore.kernel.org
 help / color / mirror / Atom feed
From: sdf@google.com
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH bpf-next] libbpf: start v1.2 development cycle
Date: Wed, 21 Dec 2022 11:12:10 -0800	[thread overview]
Message-ID: <Y6NaisLF0WoSbTgo@google.com> (raw)
In-Reply-To: <20221221180049.853365-1-andrii@kernel.org>

On 12/21, Andrii Nakryiko wrote:
> Bump current version for new development cycle to v1.2.

> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>

Acked-by: Stanislav Fomichev <sdf@google.com>

> ---
>   tools/lib/bpf/libbpf.map       | 3 +++
>   tools/lib/bpf/libbpf_version.h | 2 +-
>   2 files changed, 4 insertions(+), 1 deletion(-)

> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
> index 71bf5691a689..11c36a3c1a9f 100644
> --- a/tools/lib/bpf/libbpf.map
> +++ b/tools/lib/bpf/libbpf.map
> @@ -382,3 +382,6 @@ LIBBPF_1.1.0 {
>   		user_ring_buffer__reserve_blocking;
>   		user_ring_buffer__submit;
>   } LIBBPF_1.0.0;
> +
> +LIBBPF_1.2.0 {
> +} LIBBPF_1.1.0;
> diff --git a/tools/lib/bpf/libbpf_version.h  
> b/tools/lib/bpf/libbpf_version.h
> index e944f5bce728..1fd2eeac5cfc 100644
> --- a/tools/lib/bpf/libbpf_version.h
> +++ b/tools/lib/bpf/libbpf_version.h
> @@ -4,6 +4,6 @@
>   #define __LIBBPF_VERSION_H

>   #define LIBBPF_MAJOR_VERSION 1
> -#define LIBBPF_MINOR_VERSION 1
> +#define LIBBPF_MINOR_VERSION 2

>   #endif /* __LIBBPF_VERSION_H */
> --
> 2.30.2


  reply	other threads:[~2022-12-21 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 18:00 [PATCH bpf-next] libbpf: start v1.2 development cycle Andrii Nakryiko
2022-12-21 19:12 ` sdf [this message]
2022-12-21 19:20 ` patchwork-bot+netdevbpf

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=Y6NaisLF0WoSbTgo@google.com \
    --to=sdf@google.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.