linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: yi.zhang@redhat.com (Yi Zhang)
Subject: [PATCH] nvme-cli: print "\n" after nvme list-subsys -o json
Date: Thu, 20 Sep 2018 19:41:57 +0800	[thread overview]
Message-ID: <20180920114157.6043-1-yi.zhang@redhat.com> (raw)

Signed-off-by: Yi Zhang <yi.zhang at redhat.com>
---
 nvme-print.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/nvme-print.c b/nvme-print.c
index 17b5eaf..df7df4d 100644
--- a/nvme-print.c
+++ b/nvme-print.c
@@ -2823,6 +2823,7 @@ void json_print_nvme_subsystem_list(struct subsys_list_item *slist, int n)
 	if (i)
 		json_object_add_value_array(root, "Subsystems", subsystems);
 	json_print_object(root, NULL);
+	printf("\n");
 }
 
 static void show_registers_cap(struct nvme_bar_cap *cap)
-- 
2.17.1

             reply	other threads:[~2018-09-20 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 11:41 Yi Zhang [this message]
2018-09-20 15:17 ` [PATCH] nvme-cli: print "\n" after nvme list-subsys -o json Keith Busch

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=20180920114157.6043-1-yi.zhang@redhat.com \
    --to=yi.zhang@redhat.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 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).