archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <>
Subject: Re: [PATCH] nvme-cli: improvment critical warning format
Date: Wed, 8 Jan 2020 12:29:20 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 08, 2020 at 11:39:35AM -0600, wrote:
> From: Wen Xiong <>
> This patch improves the critical warning format with smart-log.
> Signed-off-by: Wendy Xiong<>

I merged the concept into the master. This patch looks like it was done
quite a while ago, so it didn't readily apply.

I also changed the keys for json output. These should idealy be single
words without leading whitespace. Please have a look.

linux-nvme mailing list

  reply	other threads:[~2020-01-08 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 17:39 [PATCH] nvme-cli: improvment critical warning format wenxiong
2020-01-08 20:29 ` Keith Busch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-04 19:28 wenxiong
2019-11-04 22:57 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).