From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
jiri@resnulli.us, jacob.e.keller@intel.com, sdf@google.com
Subject: Re: [PATCHv4 net-next 0/2] ynl: rename array-nest to indexed-array
Date: Sat, 06 Apr 2024 06:10:31 +0000 [thread overview]
Message-ID: <171238383181.24936.14404874871838434308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240404063114.1221532-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 4 Apr 2024 14:31:11 +0800 you wrote:
> rename array-nest to indexed-array and add un-nest sub-type support
>
> v4:
> 1. Separate binary and integer handling (Jakub Kicinski)
> 2. Update sub-type example in doc (Jakub Kicinski)
>
> v3:
> 1. fix doc title underline too short issue (Jakub Kicinski)
>
> [...]
Here is the summary with links:
- [PATCHv4,net-next,1/2] ynl: rename array-nest to indexed-array
https://git.kernel.org/netdev/net-next/c/aa6485d813ad
- [PATCHv4,net-next,2/2] ynl: support binary and integer sub-type for indexed-array
https://git.kernel.org/netdev/net-next/c/a7408b56e5f9
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-04-06 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 6:31 [PATCHv4 net-next 0/2] ynl: rename array-nest to indexed-array Hangbin Liu
2024-04-04 6:31 ` [PATCHv4 net-next 1/2] " Hangbin Liu
2024-04-04 6:31 ` [PATCHv4 net-next 2/2] ynl: support binary and integer sub-type for indexed-array Hangbin Liu
2024-04-04 6:31 ` [PATCHv3 net-next 2/2] ynl: support binary/u32 " Hangbin Liu
2024-04-06 6: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=171238383181.24936.14404874871838434308.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=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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 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.