From 31158c0dd014496f22d52c5a61428f0bfb86e98f Mon Sep 17 00:00:00 2001 From: Shuhei Matsumoto Date: Wed, 24 Apr 2019 07:49:19 +0900 Subject: [PATCH] CHANGELOG: Fix the wrong location for NVMe-oF target section Merge nvmf section into NVMe-oF target section. Change-Id: I0279392e655b719ff6229b00838fcc6406265113 Signed-off-by: Shuhei Matsumoto Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/451787 Reviewed-by: Jim Harris Reviewed-by: Changpeng Liu Tested-by: SPDK CI Jenkins --- CHANGELOG.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e4f214fda..67f8cf84d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -61,6 +61,9 @@ The size of a shared receive queue is defined by transport configuration file pa `MaxSRQDepth` and `nvmf_create_transport` RPC method parameter `max_srq_depth`. Default size is 4096. +Add model number as parameter to construct_nvmf_subsystem (-d option), +rather than using hardcoded define. + ### env The `phys_addr` parameter in spdk_malloc() and spdk_zmalloc() has been deprecated. @@ -91,11 +94,6 @@ is specified, use that specified nbd device. If it's not specified, pick availab Add Opal scan support for NVMe to check whether it supports SED Opal and dump device info. nvme_manage tool can be used to invoke this. -### nvmf - -Add model number as parameter to construct_nvmf_subsystem (-d option), -rather than using hardcoded define. - ## v19.01: ### ocf bdev