Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mlin@kernel.org (Ming Lin)
Subject: [PATCH nvme-cli] switch trtype and adrfam print
Date: Tue, 07 Jun 2016 15:07:27 -0700	[thread overview]
Message-ID: <1465337247-564-1-git-send-email-mlin@kernel.org> (raw)

From: Ming Lin <ming.l@samsung.com>

Signed-off-by: Ming Lin <ming.l at samsung.com>
---

Dave,

Could you help to take a look?
Just to make sure I don't make stupid mistake again.

 fabrics.c | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/fabrics.c b/fabrics.c
index d30bef2..0071147 100644
--- a/fabrics.c
+++ b/fabrics.c
@@ -274,18 +274,15 @@ static void print_discovery_log(struct nvmf_disc_rsp_page_hdr *log, int numrec)
 
 		printf("trtype:  ");
 		switch(e->trtype) {
-		case NVMF_ADDR_FAMILY_IP4:
-			printf("ipv4\n");
-			break;
-		case NVMF_ADDR_FAMILY_IP6:
-			printf("ipv6\n");
-			break;
-		case NVMF_ADDR_FAMILY_IB:
-			printf("ib\n");
+		case NVMF_TRTYPE_RDMA:
+			printf("rdma\n");
 			break;
-		case NVMF_ADDR_FAMILY_FC:
+		case NVMF_TRTYPE_FC:
 			printf("fc\n");
 			break;
+		case NVMF_TRTYPE_LOOP:
+			printf("loop\n");
+			break;
 		default:
 			printf("unknown\n");
 			break;
@@ -293,14 +290,17 @@ static void print_discovery_log(struct nvmf_disc_rsp_page_hdr *log, int numrec)
 
 		printf("adrfam:  ");
 		switch(e->adrfam) {
-		case NVMF_TRTYPE_RDMA:
-			printf("rdma\n");
+		case NVMF_ADDR_FAMILY_IP4:
+			printf("ipv4\n");
 			break;
-		case NVMF_TRTYPE_FC:
-			printf("fc\n");
+		case NVMF_ADDR_FAMILY_IP6:
+			printf("ipv6\n");
 			break;
-		case NVMF_TRTYPE_LOOP:
-			printf("loop\n");
+		case NVMF_ADDR_FAMILY_IB:
+			printf("ib\n");
+			break;
+		case NVMF_ADDR_FAMILY_FC:
+			printf("fc\n");
 			break;
 		default:
 			printf("unknown\n");
-- 
1.9.1

                 reply	other threads:[~2016-06-07 22:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1465337247-564-1-git-send-email-mlin@kernel.org \
    --to=mlin@kernel.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