archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <>
To: Jens Axboe <>
Subject: [GIT PULL] nvme-5.5, second pull
Date: Fri, 22 Nov 2019 02:36:35 +0900	[thread overview]
Message-ID: <> (raw)

Hi Jens,

We've accumulated a few new patches since our initial 5.5 pull request
ready for the next merge window:

 - The only new feature is the optional hwmon support for nvme (Guenter
   and Akinobu)

 - A universal work-around for controllers reading discard payloads
   beyond the range boundary (Eduard)

 - Chaitanya graciously agreed to share the target driver maintance

The following changes since commit 64fab7290dc3561729bbc1e35895a517eb2e549e:

  nvme: Fix parsing of ANA log page (2019-11-04 10:56:42 -0700)

are available in the Git repository at:

  git:// nvme-5.5

for you to fetch changes up to 6c6aa2f26c6813af38d88718881c0307bb9a54c0:

  nvme: hwmon: add quirk to avoid changing temperature threshold (2019-11-22 02:21:08 +0900)

Akinobu Mita (2):
      nvme: hwmon: provide temperature min and max values for each sensor
      nvme: hwmon: add quirk to avoid changing temperature threshold

Christoph Hellwig (1):
      nvmet: add another maintainer

Eduard Hasenleithner (1):
      nvme: Discard workaround for non-conformant devices

Guenter Roeck (1):
      nvme: Add hardware monitoring support

 MAINTAINERS                |   1 +
 drivers/nvme/host/Kconfig  |  10 ++
 drivers/nvme/host/Makefile |   1 +
 drivers/nvme/host/core.c   |  18 +++-
 drivers/nvme/host/hwmon.c  | 259 +++++++++++++++++++++++++++++++++++++++++++++
 drivers/nvme/host/nvme.h   |  13 +++
 drivers/nvme/host/pci.c    |   3 +-
 include/linux/nvme.h       |   6 ++
 8 files changed, 307 insertions(+), 4 deletions(-)
 create mode 100644 drivers/nvme/host/hwmon.c

Linux-nvme mailing list

             reply	other threads:[~2019-11-21 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 17:36 Keith Busch [this message]
2019-11-21 17:53 ` [GIT PULL] nvme-5.5, second pull Jens Axboe

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