Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Ambardar <tony.ambardar@gmail.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
	andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org,
	iii@linux.ibm.com, qmo@kernel.org
Subject: Re: [PATCH bpf-next v6 0/8] libbpf, selftests/bpf: Support cross-endian usage
Date: Fri, 27 Sep 2024 22:00:33 +0000	[thread overview]
Message-ID: <172747443327.2094989.6626660527565870189.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1726475448.git.tony.ambardar@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 16 Sep 2024 01:37:39 -0700 you wrote:
> Hello all,
> 
> This patch series targets a long-standing BPF usability issue - the lack
> of general cross-compilation support - by enabling cross-endian usage of
> libbpf and bpftool, as well as supporting cross-endian build targets for
> selftests/bpf.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/8] libbpf: Improve log message formatting
    https://git.kernel.org/bpf/bpf-next/c/86eb7eb4fbfc
  - [bpf-next,v6,2/8] libbpf: Fix header comment typos for BTF.ext
    https://git.kernel.org/bpf/bpf-next/c/4977b35bfd4b
  - [bpf-next,v6,3/8] libbpf: Fix output .symtab byte-order during linking
    https://git.kernel.org/bpf/bpf-next/c/a91c9b9697ff
  - [bpf-next,v6,4/8] libbpf: Support BTF.ext loading and output in either endianness
    https://git.kernel.org/bpf/bpf-next/c/14a76da84b18
  - [bpf-next,v6,5/8] libbpf: Support opening bpf objects of either endianness
    https://git.kernel.org/bpf/bpf-next/c/f9292d6570d5
  - [bpf-next,v6,6/8] libbpf: Support linking bpf objects of either endianness
    https://git.kernel.org/bpf/bpf-next/c/ab4184fd1bb8
  - [bpf-next,v6,7/8] libbpf: Support creating light skeleton of either endianness
    https://git.kernel.org/bpf/bpf-next/c/a1cb9abcfec4
  - [bpf-next,v6,8/8] selftests/bpf: Support cross-endian building
    https://git.kernel.org/bpf/bpf-next/c/4fd5a501e1d0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-27 22:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  8:37 [PATCH bpf-next v6 0/8] libbpf, selftests/bpf: Support cross-endian usage Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 1/8] libbpf: Improve log message formatting Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 2/8] libbpf: Fix header comment typos for BTF.ext Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 3/8] libbpf: Fix output .symtab byte-order during linking Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 4/8] libbpf: Support BTF.ext loading and output in either endianness Tony Ambardar
2024-09-27 21:47   ` Andrii Nakryiko
2024-09-16  8:37 ` [PATCH bpf-next v6 5/8] libbpf: Support opening bpf objects of " Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 6/8] libbpf: Support linking " Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 7/8] libbpf: Support creating light skeleton " Tony Ambardar
2024-09-16  8:37 ` [PATCH bpf-next v6 8/8] selftests/bpf: Support cross-endian building Tony Ambardar
2024-09-27 22:00 ` patchwork-bot+netdevbpf [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=172747443327.2094989.6626660527565870189.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=iii@linux.ibm.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tony.ambardar@gmail.com \
    --cc=yonghong.song@linux.dev \
    /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