From: Parav Pandit <parav@nvidia.com>
To: <dsahern@gmail.com>, <stephen@networkplumber.org>,
<netdev@vger.kernel.org>
Cc: Parav Pandit <parav@nvidia.com>
Subject: [PATCH iproute2-next 0/4] devlink: Use utils helpers
Date: Mon, 1 Mar 2021 12:56:50 +0200 [thread overview]
Message-ID: <20210301105654.291949-1-parav@nvidia.com> (raw)
This series uses utils helper for socket operations, string
processing and print error messages.
Patch summary:
Patch-1 uses utils library helper for string split and string search
Patch-2 extends library for socket receive operation
Patch-3 converts devlink to use socket helpers from utlis library
Patch-4 print error when user provides invalid flavour or state
Parav Pandit (4):
devlink: Use library provided string processing APIs
utils: Introduce helper routines for generic socket recv
devlink: Use generic socket helpers from library
devlink: Add error print when unknown values specified
devlink/devlink.c | 365 ++++++++++++++++++++------------------------
devlink/mnlg.c | 121 ++-------------
devlink/mnlg.h | 13 +-
include/mnl_utils.h | 6 +
lib/mnl_utils.c | 25 ++-
5 files changed, 203 insertions(+), 327 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-01 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:56 Parav Pandit [this message]
2021-03-01 10:56 ` [PATCH iproute2-next 1/4] devlink: Use library provided string processing APIs Parav Pandit
2021-03-01 10:56 ` [PATCH iproute2-next 2/4] utils: Introduce helper routines for generic socket recv Parav Pandit
2021-03-01 10:56 ` [PATCH iproute2-next 3/4] devlink: Use generic socket helpers from library Parav Pandit
2021-03-01 10:56 ` [PATCH iproute2-next 4/4] devlink: Add error print when unknown values specified Parav Pandit
2021-03-03 4:02 ` [PATCH iproute2-next 0/4] devlink: Use utils helpers David Ahern
2021-03-03 4:10 ` patchwork-bot+netdevbpf
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=20210301105654.291949-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--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).