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, donald.hunter@gmail.com, sdf@fomichev.me
Subject: Re: [PATCH net-next v2 1/2] selftests: net: rebuild YNL if dependencies changed
Date: Tue, 15 Oct 2024 01:10:38 +0000 [thread overview]
Message-ID: <172895463899.686374.7630398528769381304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241011230311.2529760-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 11 Oct 2024 16:03:10 -0700 you wrote:
> Try to rebuild YNL if either user added a new family or the specs
> of the families have changed. Stanislav's ncdevmem cause a false
> positive build failure in NIPA because libynl.a isn't rebuilt
> after ethtool is added to YNL_GENS.
>
> Note that sha1sum is already used in other parts of the build system.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] selftests: net: rebuild YNL if dependencies changed
https://git.kernel.org/netdev/net-next/c/0cb06dc6c42b
- [net-next,v2,2/2] selftests: net: move EXTRA_CLEAN of libynl.a into ynl.mk
https://git.kernel.org/netdev/net-next/c/60b4d49b9621
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-10-15 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 23:03 [PATCH net-next v2 1/2] selftests: net: rebuild YNL if dependencies changed Jakub Kicinski
2024-10-11 23:03 ` [PATCH net-next v2 2/2] selftests: net: move EXTRA_CLEAN of libynl.a into ynl.mk Jakub Kicinski
2024-10-11 23:29 ` Stanislav Fomichev
2024-10-15 1:10 ` 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=172895463899.686374.7630398528769381304.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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).