All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH rdma-next 0/5] Refactor RDMA netlink infrastructure
Date: Thu,  8 Jun 2017 17:38:47 +0300	[thread overview]
Message-ID: <20170608143852.9072-1-leon@kernel.org> (raw)

The following patch set is a preparation to addition of
netlink handlers to support RDMA tool. It simplifies the code,
removes useless client infrastructure, concentrates netlink validity
checks and allows future patches to remove a lot of dead code
from iwcm* code base (all operations related to nl_clients).

It is based on already sent to the mailing list patch [1]
"Revert "IB/core: Add flow control to the portmapper netlink calls""

[1] https://patchwork.kernel.org/patch/9752865/

Available in the "topic/rdmatool-rfc-v1" topic branch of this git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git

Or for browsing:
https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=topic/rdmatool-rfc-v1

Leon Romanovsky (5):
  RDMA/netlink: Remove netlink clients infrastructure
  RDMA/netlink: Remove redundant owner option for netlink callbacks
  RDMA/netlink: Avoid double pass for RDMA netlink messages
  RDMA/iwcm: Remove useless check of nelink client validity
  RDMA/iwcm: Remove extra EXPORT_SYMBOLS

 drivers/infiniband/core/cma.c       |   9 +-
 drivers/infiniband/core/device.c    |  41 ++----
 drivers/infiniband/core/iwcm.c      |  10 +-
 drivers/infiniband/core/iwpm_msg.c  |  12 --
 drivers/infiniband/core/iwpm_util.c |  11 --
 drivers/infiniband/core/netlink.c   | 248 +++++++++++++++++++-----------------
 include/rdma/rdma_netlink.h         |  18 +--
 7 files changed, 151 insertions(+), 198 deletions(-)

--
2.12.2

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-06-08 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 14:38 Leon Romanovsky [this message]
     [not found] ` <20170608143852.9072-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-08 14:38   ` [PATCH rdma-next 1/5] RDMA/netlink: Remove netlink clients infrastructure Leon Romanovsky
     [not found]     ` <20170608143852.9072-2-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-08 15:29       ` Bart Van Assche
     [not found]         ` <88fb8d57-cd02-78bc-3045-c09f62c280b9-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-06-08 17:51           ` Leon Romanovsky
2017-06-08 14:38   ` [PATCH rdma-next 2/5] RDMA/netlink: Remove redundant owner option for netlink callbacks Leon Romanovsky
2017-06-08 14:38   ` [PATCH rdma-next 3/5] RDMA/netlink: Avoid double pass for RDMA netlink messages Leon Romanovsky
2017-06-08 14:38   ` [PATCH rdma-next 4/5] RDMA/iwcm: Remove useless check of nelink client validity Leon Romanovsky
2017-06-08 14:38   ` [PATCH rdma-next 5/5] RDMA/iwcm: Remove extra EXPORT_SYMBOLS Leon Romanovsky

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=20170608143852.9072-1-leon@kernel.org \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.