All of lore.kernel.org
 help / color / mirror / Atom feed
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 v1 2/4] rdma: Introduce command execution helper with required device name
Date: Fri, 2 Nov 2018 10:43:38 -0600	[thread overview]
Message-ID: <d6ef5712-6ef2-93b8-ef30-0dd106e984aa@gmail.com> (raw)
In-Reply-To: <20181031071758.6178-3-leon@kernel.org>

On 10/31/18 1:17 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
> 
> In contradiction to various show commands, the set command explicitly
> requires to use device name as an argument. Provide new command
> execution helper which enforces it.
> 
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> Reviewed-by: Steve Wise <swise@opengridcomputing.com>
> ---
>  rdma/rdma.h  |  1 +
>  rdma/utils.c | 10 ++++++++++
>  2 files changed, 11 insertions(+)
> 

applied to iproute2-next. Thanks

  reply	other threads:[~2018-11-02 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  7:17 [PATCH iproute2-next v1 0/4] rdma: IB device rename Leon Romanovsky
2018-10-31  7:17 ` [PATCH iproute2-next v1 1/4] rdma: Update kernel include file to support IB device renaming Leon Romanovsky
2018-11-02 16:43   ` David Ahern
2018-10-31  7:17 ` [PATCH iproute2-next v1 2/4] rdma: Introduce command execution helper with required device name Leon Romanovsky
2018-11-02 16:43   ` David Ahern [this message]
2018-10-31  7:17 ` [PATCH iproute2-next v1 3/4] rdma: Add an option to rename IB device interface Leon Romanovsky
2018-11-02 16:43   ` David Ahern
2018-10-31  7:17 ` [PATCH iproute2-next v1 4/4] rdma: Document IB device renaming option Leon Romanovsky
2018-11-02 16:47   ` David Ahern
2018-11-04 11:12     ` 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=d6ef5712-6ef2-93b8-ef30-0dd106e984aa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.