From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@gmail.com>
Cc: swise@opengridcomputing.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] rdma: fix header files
Date: Fri, 4 May 2018 21:58:00 -0700 [thread overview]
Message-ID: <20180504215800.41b8467a@xeon-e3> (raw)
In-Reply-To: <d51c9746-d3e9-48f5-fc93-b63e4c5c7a8c@gmail.com>
On Fri, 4 May 2018 16:13:07 -0600
David Ahern <dsahern@gmail.com> wrote:
> On 5/4/18 3:56 PM, Stephen Hemminger wrote:
> > All user api headers in iproute2 should be in include/uapi
> > so that script can be used to put correct sanitized kernel headers
> > there. And the header files for rdma must be a complete set; if one
> > header file includes another, all must be present.
> >
> > This fixes build on older distributions, and Windows Services
> > for Linux.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > include/uapi/rdma/ib_user_sa.h | 77 ++
> > include/uapi/rdma/ib_user_verbs.h | 1210 +++++++++++++++++
> > .../uapi/rdma/rdma_netlink.h | 13 +
> > .../uapi/rdma/rdma_user_cm.h | 6 +-
> > 4 files changed, 1303 insertions(+), 3 deletions(-)
> > create mode 100644 include/uapi/rdma/ib_user_sa.h
> > create mode 100644 include/uapi/rdma/ib_user_verbs.h
> > rename {rdma/include => include}/uapi/rdma/rdma_netlink.h (95%)
> > rename {rdma/include => include}/uapi/rdma/rdma_user_cm.h (98%)
> >
>
> Stephen:
>
> Per a recent discussion the RDMA folks need to take ownership of the
> uapi files. RDMA features do not hit Dave's net-next tree so the rdma
> code can never hit iproute2-next during a dev cycle.
I want all uapi headers in include/uapi because it avoids possible overlap problems,
During the linux-net/linus release cycle they should match what is Linus's tree.
During the net-next they can come from two sources.
next prev parent reply other threads:[~2018-05-05 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 21:56 [PATCH iproute2] rdma: fix header files Stephen Hemminger
2018-05-04 22:13 ` David Ahern
2018-05-05 4:58 ` Stephen Hemminger [this message]
2018-05-05 15:17 ` David Ahern
2018-05-07 14:45 ` Stephen Hemminger
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=20180504215800.41b8467a@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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).