From: patchwork-bot+netdevbpf@kernel.org
To: Cupertino Miranda <cupertino.miranda@oracle.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii.nakryiko@gmail.com, eddyz87@gmail.com,
yonghong.song@linux.dev, david.faust@oracle.com,
jose.marchesi@oracle.com, elena.zannoni@oracle.com
Subject: Re: [PATCH bpf-next v2 0/2] Fix number of arguments in test
Date: Tue, 07 May 2024 21:50:29 +0000 [thread overview]
Message-ID: <171511862913.23249.18015844007588719916.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240507122220.207820-1-cupertino.miranda@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 7 May 2024 13:22:18 +0100 you wrote:
> Hi everyone,
>
> This is a new version based on comments.
>
> Regards,
> Cupertino
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: Add CFLAGS per source file and runner
https://git.kernel.org/bpf/bpf-next/c/207cf6e649ee
- [bpf-next,v2,2/2] selftests/bpf: Change functions definitions to support GCC
https://git.kernel.org/bpf/bpf-next/c/b2e086cb28aa
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-05-07 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 12:22 [PATCH bpf-next v2 0/2] Fix number of arguments in test Cupertino Miranda
2024-05-07 12:22 ` [PATCH bpf-next v2 1/2] selftests/bpf: Add CFLAGS per source file and runner Cupertino Miranda
2024-05-07 12:22 ` [PATCH bpf-next v2 2/2] selftests/bpf: Change functions definitions to support GCC Cupertino Miranda
2024-05-07 21: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=171511862913.23249.18015844007588719916.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).