From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, corbet@lwn.net, jiri@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org,
stephen@networkplumber.org
Subject: Re: [iproute2-next 0/2] devlink: remove dl_argv_parse_put
Date: Wed, 24 Aug 2022 16:00:15 +0000 [thread overview]
Message-ID: <166135681554.11375.11013152056749467118.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220818211521.169569-1-jacob.e.keller@intel.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 18 Aug 2022 14:15:19 -0700 you wrote:
> This series removes the dl_argv_parse_put function which both parses the
> command line arguments and places them into the netlink header.
>
> This was originally sent as an RFC at
> https://lore.kernel.org/netdev/20220805234155.2878160-1-jacob.e.keller@intel.com/
>
> Since there is some ongoing work around policy code being generated from
> YAML, I thought it best to wait on the devlink policy portion of this series
> for now.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] devlink: use dl_no_arg instead of checking dl_argc == 0
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=0ce6ae80c380
- [iproute2-next,2/2] devlink: remove dl_argv_parse_put
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=8ed3d1687dc1
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:[~2022-08-24 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:15 [iproute2-next 0/2] devlink: remove dl_argv_parse_put Jacob Keller
2022-08-18 21:15 ` [iproute2-next 1/2] devlink: use dl_no_arg instead of checking dl_argc == 0 Jacob Keller
2022-08-19 8:26 ` Jiri Pirko
2022-08-18 21:15 ` [iproute2-next 2/2] devlink: remove dl_argv_parse_put Jacob Keller
2022-08-19 8:27 ` Jiri Pirko
2022-08-19 8:27 ` [iproute2-next 0/2] " Jiri Pirko
2022-08-24 16:00 ` 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=166135681554.11375.11013152056749467118.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
/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.