[GIT PULL] nvme-5.5

[GIT PULL] nvme-5.5

[Keith Busch]

Hi Jens,

This is our first pull request for the upcoming 5.5 merge window.
Nothing major on new features here: mainly syncing with spec
updates, various code clean ups, and a few minor fixes.

This tree was based on linux-block/for-5.5/block. Please let me know if
you prefer these to be based on the for-5.x/drivers in the future and
I'll be sure to use that as a starting point.

The following changes since commit d2c9be89f8ebe7ebcc97676ac40f8dec1cf9b43a:

  blk-mq: make sure that line break can be printed (2019-11-04 07:14:10 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git for-5.5/nvme

for you to fetch changes up to 16c64b4913a4c1a521cb85c88b25d7015a591451:

  nvme: Fix parsing of ANA log page (2019-11-05 01:17:58 +0900)

----------------------------------------------------------------
Christoph Hellwig (8):
      nvmet: Introduce common execute function for get_log_page and identify
      nvmet: Cleanup discovery execute handlers
      nvmet: Introduce nvmet_dsm_len() helper
      nvmet: Remove the data_len field from the nvmet_req struct
      nvmet: Open code nvmet_req_execute()
      nvmet: clean up command parsing a bit
      nvmet: add plugging for read/write when ns is bdev
      nvmet: stop using bio_set_op_attrs

Damien Le Moal (2):
      nvme: Cleanup and rename nvme_block_nr()
      nvme: Introduce nvme_lba_to_sect()

Geert Uytterhoeven (1):
      nvme-pci: Spelling s/resdicovered/rediscovered/

Israel Rukshin (4):
      nvme: introduce nvme_is_aen_req function
      nvmet: use bio_io_error instead of duplicating it
      nvmet: add unlikely check at nvmet_req_alloc_sgl
      nvmet-rdma: add unlikely check at nvmet_rdma_map_sgl_keyed

James Smart (5):
      nvme-fc: Sync nvme-fc header to FC-NVME-2
      nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes
      nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu
      nvme-fc: clarify error messages
      nvme-fc: ensure association_id is cleared regardless of a Disconnect LS

Logan Gunthorpe (2):
      nvmet-tcp: Don't check data_len in nvmet_tcp_map_data()
      nvmet-tcp: Don't set the request's data_len

Max Gurtovoy (2):
      nvme: introduce "Command Aborted By host" status code
      nvme: move common call to nvme_cleanup_cmd to core layer

Prabhath Sajeepa (1):
      nvme: Fix parsing of ANA log page

Revanth Rajashekar (1):
      nvme: resync include/linux/nvme.h with nvmecli

Sagi Grimberg (1):
      nvmet: fill discovery controller sn, fr and mn correctly

 drivers/nvme/host/core.c          |  24 ++---
 drivers/nvme/host/fc.c            |  49 +++++-----
 drivers/nvme/host/multipath.c     |  13 ++-
 drivers/nvme/host/nvme.h          |  20 ++++-
 drivers/nvme/host/pci.c           |   6 +-
 drivers/nvme/host/rdma.c          |  16 ++--
 drivers/nvme/host/tcp.c           |   4 +-
 drivers/nvme/target/admin-cmd.c   | 133 +++++++++++++++++-----------
 drivers/nvme/target/core.c        |  20 ++---
 drivers/nvme/target/discovery.c   |  70 ++++++++-------
 drivers/nvme/target/fabrics-cmd.c |  15 +++-
 drivers/nvme/target/fc.c          |  31 ++++---
 drivers/nvme/target/io-cmd-bdev.c |  43 +++++----
 drivers/nvme/target/io-cmd-file.c |  20 +++--
 drivers/nvme/target/loop.c        |   7 +-
 drivers/nvme/target/nvmet.h       |  10 ++-
 drivers/nvme/target/rdma.c        |   8 +-
 drivers/nvme/target/tcp.c         |  14 ++-
 include/linux/nvme-fc.h           | 182 ++++++++++++++++++++++++++++----------
 include/linux/nvme.h              |  54 ++++++++++-
 20 files changed, 477 insertions(+), 262 deletions(-)

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

Re: [GIT PULL] nvme-5.5

[Jens Axboe]

On 11/4/19 10:00 AM, Keith Busch wrote:
> Hi Jens,
> 
> This is our first pull request for the upcoming 5.5 merge window.
> Nothing major on new features here: mainly syncing with spec
> updates, various code clean ups, and a few minor fixes.
> 
> This tree was based on linux-block/for-5.5/block. Please let me know if
> you prefer these to be based on the for-5.x/drivers in the future and
> I'll be sure to use that as a starting point.

Yeah, I'd prefer if it was against for-5.x/drivers going forward to keep
a cleaner separation between core and driver changes. I can just pull
these and apply them to for-5.5/drivers, not a big deal.

-- 
Jens Axboe


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme