All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
	<martin.lau@kernel.org>
Cc: <andrii@kernel.org>, <kernel-team@meta.com>
Subject: [PATCH v3 bpf-next 0/4] Prepare veristat for packaging
Date: Fri, 31 Mar 2023 15:24:01 -0700	[thread overview]
Message-ID: <20230331222405.3468634-1-andrii@kernel.org> (raw)

This patch set relicenses veristat.c to dual GPL-2.0/BSD-2 license and
prepares it to be mirrored to Github at libbpf/veristat repo.

Few small issues in the source code are fixed, found during Github sync
preparetion.

v2->v3:
  - fix few warnings about uninitialized variable uses;
v1->v2:
  - drop linux/compiler.h and define own ARRAY_SIZE macro;

Andrii Nakryiko (4):
  veristat: relicense veristat.c as dual GPL-2.0-only or BSD-2-Clause
    licensed
  veristat: improve version reporting
  veristat: avoid using kernel-internal headers
  veristat: small fixed found in -O2 mode

 tools/testing/selftests/bpf/veristat.c | 30 +++++++++++++++++++++-----
 1 file changed, 25 insertions(+), 5 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-03-31 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 22:24 Andrii Nakryiko [this message]
2023-03-31 22:24 ` [PATCH v3 bpf-next 1/4] veristat: relicense veristat.c as dual GPL-2.0-only or BSD-2-Clause licensed Andrii Nakryiko
2023-03-31 22:24 ` [PATCH v3 bpf-next 2/4] veristat: improve version reporting Andrii Nakryiko
2023-03-31 22:24 ` [PATCH v3 bpf-next 3/4] veristat: avoid using kernel-internal headers Andrii Nakryiko
2023-03-31 22:24 ` [PATCH v3 bpf-next 4/4] veristat: small fixed found in -O2 mode Andrii Nakryiko
2023-04-01 16:10 ` [PATCH v3 bpf-next 0/4] Prepare veristat for packaging 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=20230331222405.3468634-1-andrii@kernel.org \
    --to=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    /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.