public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory
Date: Wed, 14 Sep 2016 11:27:26 +0300	[thread overview]
Message-ID: <1473841649-8923-1-git-send-email-leon@kernel.org> (raw)

The consolidate library revealed the fact that vendor specific
structures and defines are copy/pasted between kernel and user-space,
instead of sharing.

This RFC was tested by compilation only and not-ready for merge yet.

Leon Romanovsky (3):
  IB/mlx5: Move and decouple user vendor structures
  IB/core: Export mlx5 vendor specific strucutres
  MAINTAINERS: Add mlx5 uapi file

 MAINTAINERS                            |   1 +
 drivers/infiniband/hw/mlx5/cq.c        |   1 -
 drivers/infiniband/hw/mlx5/main.c      |   1 -
 drivers/infiniband/hw/mlx5/mlx5_ib.h   |  37 +++++
 drivers/infiniband/hw/mlx5/mr.c        |   1 -
 drivers/infiniband/hw/mlx5/qp.c        |   1 -
 drivers/infiniband/hw/mlx5/srq.c       |   1 -
 drivers/infiniband/hw/mlx5/user.h      | 281 ---------------------------------
 include/uapi/rdma/Kbuild               |   1 +
 include/uapi/rdma/providers/Kbuild     |   2 +
 include/uapi/rdma/providers/mlx5-abi.h | 242 ++++++++++++++++++++++++++++
 11 files changed, 283 insertions(+), 286 deletions(-)
 delete mode 100644 drivers/infiniband/hw/mlx5/user.h
 create mode 100644 include/uapi/rdma/providers/Kbuild
 create mode 100644 include/uapi/rdma/providers/mlx5-abi.h

--
2.7.4

--
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:[~2016-09-14  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:27 Leon Romanovsky [this message]
     [not found] ` <1473841649-8923-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-09-14  8:27   ` [RFC rdma-next 1/3] IB/mlx5: Move and decouple user vendor structures Leon Romanovsky
2016-09-14  8:27   ` [RFC rdma-next 2/3] IB/core: Export mlx5 vendor specific strucutres Leon Romanovsky
     [not found]     ` <1473841649-8923-3-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-09-15  6:13       ` Christoph Hellwig
     [not found]         ` <20160915061336.GA4869-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-09-15  6:25           ` Leon Romanovsky
2016-09-15 16:17           ` Jason Gunthorpe
2016-09-14  8:27   ` [RFC rdma-next 3/3] MAINTAINERS: Add mlx5 uapi file Leon Romanovsky
2016-09-14 17:21   ` [RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory Jason Gunthorpe
     [not found]     ` <20160914172145.GI16014-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-14 19:46       ` Laurence Oberman
     [not found]         ` <1495514480.6044744.1473882367077.JavaMail.zimbra-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-15  5:06           ` Leon Romanovsky
2016-09-15  5:02       ` 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=1473841649-8923-1-git-send-email-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox