From: patchwork-bot+netdevbpf@kernel•org
To: Jiri Pirko <jiri@resnulli•us>
Cc: netdev@vger•kernel.org, kuba@kernel•org, pabeni@redhat•com,
davem@davemloft•net, edumazet@google•com,
donald.hunter@gmail•com
Subject: Re: [patch net-next v3 0/2] tools: ynl-gen: lift type requirement for attribute subsets
Date: Tue, 10 Oct 2023 02:50:25 +0000 [thread overview]
Message-ID: <169690622540.548.9799997208397355098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231006114436.1725425-1-jiri@resnulli.us>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 6 Oct 2023 13:44:34 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia•com>
>
> Remove the requirement from schema files to specify the "type" for
> attribute subsets and adjust existing schema files.
>
> Jiri Pirko (2):
> tools: ynl-gen: lift type requirement for attribute subsets
> netlink: specs: remove redundant type keys from attributes in subsets
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] tools: ynl-gen: lift type requirement for attribute subsets
https://git.kernel.org/netdev/net-next/c/e18f3dc2beaa
- [net-next,v3,2/2] netlink: specs: remove redundant type keys from attributes in subsets
https://git.kernel.org/netdev/net-next/c/7049fd5df78c
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:[~2023-10-10 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 11:44 [patch net-next v3 0/2] tools: ynl-gen: lift type requirement for attribute subsets Jiri Pirko
2023-10-06 11:44 ` [patch net-next v3 1/2] " Jiri Pirko
2023-10-06 15:00 ` Jakub Kicinski
2023-10-06 16:55 ` Jiri Pirko
2023-10-06 19:33 ` Jakub Kicinski
2023-10-06 11:44 ` [patch net-next v3 2/2] netlink: specs: remove redundant type keys from attributes in subsets Jiri Pirko
2023-10-10 2: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=169690622540.548.9799997208397355098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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