public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@pm.me>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii.nakryiko@gmail.com,
	eddyz87@gmail.com, daniel@iogearbox.net, mykolal@fb.com
Subject: Re: [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects
Date: Fri, 19 Jul 2024 18:20:30 +0000	[thread overview]
Message-ID: <172141323037.13293.5496223993427449959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <VJihUTnvtwEgv_mOnpfy7EgD9D2MPNoHO-MlANeLIzLJPGhDeyOuGKIYyKgk0O6KPjfM-MuhtvPwZcngN8WFqbTnTRyCSMc2aMZ1ODm1T_g=@pm.me>

Hello:

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

On Thu, 18 Jul 2024 22:57:43 +0000 you wrote:
> Make use of -M compiler options when building .test.o objects to
> generate .d files and avoid re-building all tests every time.
> 
> Previously, if a single test bpf program under selftests/bpf/progs/*.c
> has changed, make would rebuild all the *.bpf.o, *.skel.h and *.test.o
> objects, which is a lot of unnecessary work.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4] selftests/bpf: use auto-dependencies for test objects
    https://git.kernel.org/bpf/bpf-next/c/a3cc56cd2c20

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-07-19 18:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 22:57 [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects Ihor Solodrai
2024-07-19 18:18 ` Andrii Nakryiko
2024-07-19 19:03   ` Ihor Solodrai
2024-07-19 21:54   ` Tony Ambardar
2024-07-19 22:25     ` Andrii Nakryiko
2024-07-19 23:21       ` [PATCH bpf-next v1] selftests/bpf: Fix wrong binary in Makefile log output Tony Ambardar
2024-07-20  0:14         ` bot+bpf-ci
2024-07-20  1:23         ` Eduard Zingerman
2024-07-20  2:57         ` Andrii Nakryiko
2024-07-20  5:23           ` Tony Ambardar
2024-07-23  1:35             ` Tony Ambardar
2024-07-23  1:37               ` Eduard Zingerman
2024-07-23 20:28                 ` Andrii Nakryiko
2024-07-20  5:25         ` [PATCH bpf-next v2] " Tony Ambardar
2024-07-20  5:49           ` bot+bpf-ci
2024-07-22 15:17           ` bot+bpf-ci
2024-07-22 19:58           ` bot+bpf-ci
2024-07-23  1:40           ` bot+bpf-ci
2024-07-23  2:46           ` bot+bpf-ci
2024-07-23 20:30           ` patchwork-bot+netdevbpf
2024-07-19 18:20 ` patchwork-bot+netdevbpf [this message]
2024-07-23  0:39   ` [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects Alexei Starovoitov
2024-07-23  0:57     ` Eduard Zingerman
2024-07-23  1:49       ` Eduard Zingerman
2024-07-23  1:50       ` Ihor Solodrai
2024-07-23 19:25         ` Ihor Solodrai
2024-07-23 20:02           ` Andrii Nakryiko
2024-07-23 20:11             ` Ihor Solodrai
2024-09-13 14:51   ` Björn Töpel
2024-09-13 22:33     ` Ihor Solodrai
2024-09-14 10:54       ` Björn Töpel
2024-09-15  4:47         ` Ihor Solodrai
2024-09-15 15:41           ` Björn Töpel

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=172141323037.13293.5496223993427449959.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@pm.me \
    --cc=mykolal@fb.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