From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
horms@kernel.org, sdf@fomichev.me, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] tools/ynl: add missing uapi header deps in Makefile.deps
Date: Sun, 10 May 2026 15:40:05 +0000 [thread overview]
Message-ID: <177842760554.1414591.3890317509091929731.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260508204114.205896-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 May 2026 13:41:12 -0700 you wrote:
> When syncing ynl-cpp to net-next v7.0-rc3, typelimits.h (for ethtool) and
> dev_energymodel.h had to be manually hacked into the downstream
> Makefile.deps:
>
> https://github.com/linux-netdev/ynl-cpp/pull/16/changes/94bd9656423cab7dfce73dc824f75b59ef25668d
>
> Fix the upstream Makefile.deps so that downstream copies stay in sync.
>
> [...]
Here is the summary with links:
- [net-next,1/2] tools/ynl: add missing uapi header deps in Makefile.deps
https://git.kernel.org/netdev/net/c/46e9b0224475
- [net-next,2/2] tools/ynl: add check-deps target to verify Makefile.deps completeness
(no matching commit)
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:[~2026-05-10 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 20:41 [PATCH net-next 0/2] tools/ynl: add missing uapi header deps in Makefile.deps Stanislav Fomichev
2026-05-08 20:41 ` [PATCH net-next 1/2] " Stanislav Fomichev
2026-05-08 20:41 ` [PATCH net-next 2/2] tools/ynl: add check-deps target to verify Makefile.deps completeness Stanislav Fomichev
2026-05-10 15:35 ` Jakub Kicinski
2026-05-10 15:40 ` 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=177842760554.1414591.3890317509091929731.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=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.