netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org, bjorn@rivosinc.com,
	lina.wang@mediatek.com, linux-kselftest@vger.kernel.org,
	anders.roxell@linaro.org
Subject: Re: [PATCH net-next] selftests: net: Add cross-compilation support for BPF programs
Date: Tue, 22 Nov 2022 13:00:15 +0000	[thread overview]
Message-ID: <166912201552.5123.8530809477540331372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221119171841.2014936-1-bjorn@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Sat, 19 Nov 2022 18:18:41 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> The selftests/net does not have proper cross-compilation support, and
> does not properly state libbpf as a dependency. Mimic/copy the BPF
> build from selftests/bpf, which has the nice side-effect that libbpf
> is built as well.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: net: Add cross-compilation support for BPF programs
    https://git.kernel.org/netdev/net-next/c/837a3d66d698

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



      parent reply	other threads:[~2022-11-22 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 17:18 [PATCH net-next] selftests: net: Add cross-compilation support for BPF programs Björn Töpel
2022-11-21 10:45 ` Anders Roxell
2022-11-21 16:48   ` Björn Töpel
2022-11-22  7:47     ` Anders Roxell
2022-11-22 12:54 ` Paolo Abeni
2022-11-22 13: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=166912201552.5123.8530809477540331372.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=anders.roxell@linaro.org \
    --cc=bjorn@rivosinc.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lina.wang@mediatek.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).