From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>,
David Ahern <dsahern@gmail.com>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>,
netdev <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH iproute2-next 5/9] rdma: Allow external usage of compare string routine
Date: Tue, 2 Jan 2018 11:37:21 +0200 [thread overview]
Message-ID: <20180102093725.6172-6-leon@kernel.org> (raw)
In-Reply-To: <20180102093725.6172-1-leon@kernel.org>
From: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
---
rdma/rdma.h | 2 ++
rdma/utils.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/rdma/rdma.h b/rdma/rdma.h
index e842d076..816c8ddd 100644
--- a/rdma/rdma.h
+++ b/rdma/rdma.h
@@ -84,6 +84,8 @@ void rd_free(struct rd *rd);
int rd_set_arg_to_devname(struct rd *rd);
int rd_argc(struct rd *rd);
+int strcmpx(const char *str1, const char *str2);
+
/*
* Device manipulation
*/
diff --git a/rdma/utils.c b/rdma/utils.c
index fbeffa08..a63a7c2f 100644
--- a/rdma/utils.c
+++ b/rdma/utils.c
@@ -24,7 +24,7 @@ char *rd_argv(struct rd *rd)
return *rd->argv;
}
-static int strcmpx(const char *str1, const char *str2)
+int strcmpx(const char *str1, const char *str2)
{
if (strlen(str1) > strlen(str2))
return -1;
--
2.15.1
next prev parent reply other threads:[~2018-01-02 9:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 9:37 [PATCH iproute2-next 0/9] RDMA resource tracking Leon Romanovsky
[not found] ` <20180102093725.6172-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-02 9:37 ` [PATCH iproute2-next 1/9] rdam: Add option to provide "-" sign for the port number Leon Romanovsky
[not found] ` <20180102093725.6172-2-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-03 2:46 ` David Ahern
2018-01-02 9:37 ` [PATCH iproute2-next 2/9] rdma: Make visible the number of arguments Leon Romanovsky
2018-01-02 9:37 ` [PATCH iproute2-next 6/9] rdma: Update kernel header file Leon Romanovsky
[not found] ` <20180102093725.6172-7-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-03 2:50 ` David Ahern
[not found] ` <8dc793ba-abf7-900b-02b9-0f9f468fd49f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-03 5:28 ` Leon Romanovsky
2018-01-03 5:40 ` [PATCH iproute2-next 0/9] RDMA resource tracking Leon Romanovsky
2018-01-02 9:37 ` [PATCH iproute2-next 3/9] rdma: Add filtering infrastructure Leon Romanovsky
2018-01-03 2:47 ` David Ahern
2018-01-02 9:37 ` [PATCH iproute2-next 4/9] rdma: Set pointer to device name position Leon Romanovsky
2018-01-02 9:37 ` Leon Romanovsky [this message]
2018-01-02 9:37 ` [PATCH iproute2-next 7/9] rdma: Add resource tracking summary Leon Romanovsky
2018-01-02 9:37 ` [PATCH iproute2-next 8/9] rdma: Add QP resource tracking information Leon Romanovsky
[not found] ` <20180102093725.6172-9-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-03 3:03 ` David Ahern
2018-01-02 9:37 ` [PATCH iproute2-next 9/9] rdma: Document resource tracking 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=20180102093725.6172-6-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=dsahern@gmail.com \
--cc=jgg@mellanox.com \
--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).