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: Refresh help section of resource information
Date: Thu, 1 Nov 2018 08:22:13 -0500	[thread overview]
Message-ID: <014201d471e5$e71d65e0$b55831a0$@opengridcomputing.com> (raw)
In-Reply-To: <20181101083505.25152-1-leon@kernel.org>



> -----Original Message-----
> From: Leon Romanovsky <leon@kernel.org>
> Sent: Thursday, November 1, 2018 3:35 AM
> To: 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>; Steve Wise
> <swise@opengridcomputing.com>
> Subject: [PATCH iproute2-next] rdma: Refresh help section of resource
> information
> 
> From: Leon Romanovsky <leonro@mellanox.com>
> 
> After commit 4060e4c0d257 ("rdma: Add PD resource tracking
> information"), the resource information shows PDs and MRs,
> but help pages didn't fully reflect it.
> 
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>

Oops.  Thanks.  Looks fine.

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

  reply	other threads:[~2018-11-01 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  8:35 [PATCH iproute2-next] rdma: Refresh help section of resource information Leon Romanovsky
2018-11-01 13:22 ` Steve Wise [this message]
2018-11-05 16:40 ` 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='014201d471e5$e71d65e0$b55831a0$@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).