From: David Ahern <dsahern@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
netdev <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH iproute2-next v1] rdma: Add batch command support
Date: Thu, 22 Feb 2018 15:48:19 -0700 [thread overview]
Message-ID: <1fd816a5-2f66-4317-bba6-5668638c0b08@gmail.com> (raw)
In-Reply-To: <20180222072823.25335-1-leon@kernel.org>
On 2/22/18 12:28 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Implement an option (-b) to execute RDMAtool commands
> from supplied file. This follows the same model as
> in use for ip and devlink tools, by expecting
> every new command to be on new line.
>
> These commands are expected to be without any -*
> (e.g. -d, -j, e.t.c) global flags, which should be
> called externally.
>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
>
> Changelog v0->v1:
> * Used ARRAY_SIZE instead of hardcoded value as an input to makeargs()
>
> David,
>
> This patch is based on iproute2.git because iproute2-next doesn't
> have latest restrack code. The patch itself is completely independent
> from that code and is supposed to go to -next, but it has conflicts
> (manual page and help line).
>
> Can you please merge iproute2 master into iproute2-next prior to
> applying this patch?
>
Done. And applied to iproute2-next
prev parent reply other threads:[~2018-02-22 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 7:28 [PATCH iproute2-next v1] rdma: Add batch command support Leon Romanovsky
2018-02-22 22:48 ` David Ahern [this message]
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=1fd816a5-2f66-4317-bba6-5668638c0b08@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 \
/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).