From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] selftests: net: extract BPF building logic from the Makefile
Date: Thu, 25 Apr 2024 03:50:28 +0000 [thread overview]
Message-ID: <171401702826.27021.16042743392175785852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423183542.3807234-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 23 Apr 2024 11:35:40 -0700 you wrote:
> This has been sitting in my tree for a while. I will soon add YNL/libynl
> support for networking selftests. This prompted a small cleanup of
> the selftest makefile for net/. We don't want to be piling logic
> for each library in there. YNL will get its own .mk file which can
> be included. Do the same for the BPF building section, already.
>
> No funcional changes here, just a code move and small rename.
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: net: name bpf objects consistently and simplify Makefile
https://git.kernel.org/netdev/net-next/c/6b88ce902f0b
- [net-next,2/2] selftests: net: extract BPF building logic from the Makefile
https://git.kernel.org/netdev/net-next/c/3f584c211d8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-25 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:35 [PATCH net-next 0/2] selftests: net: extract BPF building logic from the Makefile Jakub Kicinski
2024-04-23 18:35 ` [PATCH net-next 1/2] selftests: net: name bpf objects consistently and simplify Makefile Jakub Kicinski
2024-04-23 18:35 ` [PATCH net-next 2/2] selftests: net: extract BPF building logic from the Makefile Jakub Kicinski
2024-04-25 3:50 ` 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=171401702826.27021.16042743392175785852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@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).