netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Leon Romanovsky'" <leon@kernel.org>,
	"'David Ahern'" <dsahern@gmail.com>
Cc: "'Leon Romanovsky'" <leonro@mellanox.com>,
	"'netdev'" <netdev@vger.kernel.org>,
	"'RDMA mailing list'" <linux-rdma@vger.kernel.org>,
	"'Stephen Hemminger'" <stephen@networkplumber.org>
Subject: RE: [PATCH iproute2-next] rdma: Move RDMA UAPI header file to be under RDMA responsibility
Date: Sun, 25 Mar 2018 08:52:20 -0500	[thread overview]
Message-ID: <008701d3c440$7f6eb870$7e4c2950$@opengridcomputing.com> (raw)
In-Reply-To: <20180325063856.31709-1-leon@kernel.org>

> Subject: [PATCH iproute2-next] rdma: Move RDMA UAPI header file to be
> under RDMA responsibility
> 
> 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>

Reviewed-by: Steve Wise <swise@opengridcomputing.com>

  reply	other threads:[~2018-03-25 13:52 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 [this message]
2018-03-26 14:03 ` David Ahern
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='008701d3c440$7f6eb870$7e4c2950$@opengridcomputing.com' \
    --to=swise@opengridcomputing.com \
    --cc=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 \
    /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).