From: David Ahern <dsahern@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
netdev <netdev@vger.kernel.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Steve Wise <swise@opengridcomputing.com>
Subject: Re: [PATCH iproute2-next] rdma: Move RDMA UAPI header file to be under RDMA responsibility
Date: Mon, 26 Mar 2018 08:03:04 -0600 [thread overview]
Message-ID: <c1cd4d27-dce6-84d0-344d-86ff7223add8@gmail.com> (raw)
In-Reply-To: <20180325063856.31709-1-leon@kernel.org>
On 3/25/18 12:38 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> In iproute2 package, the updates of UAPIs files are performed
> after the needed feature lands in kernel's net-next tree.
>
> Such development flow created delays to the rdma tool developers,
> who uses rdma-next tree as a basis for their work.
>
> Move RDMA UAPI file to be under rdma/ folder, so whole responsibility
> of syncing this file will be on them.
>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> rdma/Makefile | 1 +
> {include => rdma/include}/uapi/rdma/rdma_netlink.h | 0
> 2 files changed, 1 insertion(+)
> rename {include => rdma/include}/uapi/rdma/rdma_netlink.h (100%)
applied to iproute2-next
next prev parent reply other threads:[~2018-03-26 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 6:38 [PATCH iproute2-next] rdma: Move RDMA UAPI header file to be under RDMA responsibility Leon Romanovsky
2018-03-25 13:52 ` Steve Wise
2018-03-26 14:03 ` David Ahern [this message]
2018-03-26 14:23 ` Steve Wise
2018-03-26 17:07 ` 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=c1cd4d27-dce6-84d0-344d-86ff7223add8@gmail.com \
--to=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).