From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Subject: Re: [PATCH rdma/wip/jgg-for-next] RDMA/netlink: Hide unimplemented NLDEV commands
Date: Wed, 31 Jan 2018 15:40:17 -0700 [thread overview]
Message-ID: <20180131224017.GA2846@ziepe.ca> (raw)
In-Reply-To: <20180130150716.16372-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Tue, Jan 30, 2018 at 05:07:16PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>
> The nldev was implemented by following devlink implementation,
> including SET/DEL/NEW commands. However these commands were not
> implemented and hence don't need to be exposed.
>
> Signed-off-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> include/uapi/rdma/rdma_netlink.h | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
Doug applied this to for-next
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-31 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:07 [PATCH rdma/wip/jgg-for-next] RDMA/netlink: Hide unimplemented NLDEV commands Leon Romanovsky
[not found] ` <20180130150716.16372-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-30 15:57 ` Jiri Pirko
2018-01-30 16:03 ` Jason Gunthorpe
[not found] ` <20180130160337.GD17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 18:18 ` Jiri Pirko
2018-01-30 18:39 ` Leon Romanovsky
2018-01-30 18:48 ` Jason Gunthorpe
2018-01-30 18:38 ` Leon Romanovsky
2018-01-31 22:40 ` Jason Gunthorpe [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=20180131224017.GA2846@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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