From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
oss-drivers@netronome.com, jiri@resnulli.us
Subject: Re: [PATCH iproute2-next 0/3] devlink: improve parameter checking, resources and namespaces
Date: Fri, 8 Nov 2019 17:40:49 -0700 [thread overview]
Message-ID: <efc9b659-e6ab-a161-c05e-6249df096119@gmail.com> (raw)
In-Reply-To: <20191105211707.10300-1-jakub.kicinski@netronome.com>
On 11/5/19 2:17 PM, Jakub Kicinski wrote:
> Hi!
>
> This set brings small fixes/improvements for devlink tool.
> First the netns reference by PID is fixed (code is in -next only).
> Next an extra check is added to catch bugs where new feature forgot
> to add required parameters to the error string table.
> Last but not least allow full range of resource sizes.
>
> These changes are required to fix kernel's devlink.sh test.
>
> Jakub Kicinski (3):
> devlink: fix referencing namespace by PID
> devlink: catch missing strings in dl_args_required
> devlink: allow full range of resource sizes
>
> devlink/devlink.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
Applied to iproute2-next. Thanks,
prev parent reply other threads:[~2019-11-09 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 21:17 [PATCH iproute2-next 0/3] devlink: improve parameter checking, resources and namespaces Jakub Kicinski
2019-11-05 21:17 ` [PATCH iproute2-next 1/3] devlink: fix referencing namespace by PID Jakub Kicinski
2019-11-06 8:51 ` Jiri Pirko
2019-11-05 21:17 ` [PATCH iproute2-next 2/3] devlink: catch missing strings in dl_args_required Jakub Kicinski
2019-11-06 8:52 ` Jiri Pirko
2019-11-05 21:17 ` [PATCH iproute2-next 3/3] devlink: allow full range of resource sizes Jakub Kicinski
2019-11-06 8:53 ` Jiri Pirko
2019-11-09 0:40 ` David Ahern [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=efc9b659-e6ab-a161-c05e-6249df096119@gmail.com \
--to=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 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).