mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: zhenwei pi <pizhenwei@bytedance.com>
To: kbusch@kernel.org, hch@lst.de
Cc: sagi@grimberg.me, axboe@fb.com, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] nvme: enable smart AEN
Date: Mon, 9 May 2022 20:41:40 +0800	[thread overview]
Message-ID: <9d51e5fc-6ab1-84e0-9956-8a084e0d2110@bytedance.com> (raw)
In-Reply-To: <20220507065026.260306-1-pizhenwei@bytedance.com>

Hi,

Sorry, I misunderstand OAES[7:0], only the first patch "nvme: introduce 
bit 5 of smart critical warning" is available.

On 5/7/22 14:50, zhenwei pi wrote:
> Hi,
> 
> There are several changes in this series:
> - Add missing NVME_SMART_CRIT_PMR_UNRELIABLE enum type.
> - Add missing NVME_AEN_CFG_SMART_CRIT_* enum types.
> - Enable smart AEN.
> 
> zhenwei pi (3):
>    nvme: introduce bit 5 of smart critical warning
>    nvme: introduce smart bits of aen cfg
>    nvme: enable smart AEN
> 
>   drivers/nvme/host/core.c |  6 +++++-
>   include/linux/nvme.h     | 20 ++++++++++++++++----
>   2 files changed, 21 insertions(+), 5 deletions(-)
> 

-- 
zhenwei pi

  parent reply	other threads:[~2022-05-09 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07  6:50 zhenwei pi
2022-05-07  6:50 ` [PATCH 1/3] nvme: introduce bit 5 of smart critical warning zhenwei pi
2022-05-10  5:49   ` Christoph Hellwig
2022-05-10  6:44     ` zhenwei pi
2022-05-07  6:50 ` [PATCH 2/3] nvme: introduce smart bits of aen cfg zhenwei pi
2022-05-07  6:50 ` [PATCH 3/3] nvme: enable smart AEN zhenwei pi
2022-05-09 12:41 ` zhenwei pi [this message]
2022-05-10 19:13 ` [PATCH 0/3] " Sagi Grimberg
2022-05-11  0:02   ` zhenwei pi

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=9d51e5fc-6ab1-84e0-9956-8a084e0d2110@bytedance.com \
    --to=pizhenwei@bytedance.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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

all inboxes | Powered by JetHome®