diff options
Diffstat (limited to 'debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch')
| -rw-r--r-- | debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch b/debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch index 0a406e80..75e706bc 100644 --- a/debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch +++ b/debian/patches/0006-imsm-pass-already-existing-map-to-imsm_num_data_memb.patch @@ -1,7 +1,8 @@ From 9529d3436771d9f38884861683dee3b40ab9d180 Mon Sep 17 00:00:00 2001 From: Mariusz Dabrowski <mariusz.dabrowski@intel.com> Date: Thu, 5 Apr 2018 13:38:37 +0200 -Subject: [PATCH 6/9] imsm: pass already existing map to imsm_num_data_members +Subject: [PATCH 06/26] imsm: pass already existing map to + imsm_num_data_members In almost every place where imsm_num_data_members is called there is already existing map so it can be used it to avoid mistake when specifying @@ -174,5 +175,5 @@ index fe2a705b..3fc3cf4c 100644 chunk = __le16_to_cpu(map_src->blocks_per_strip) * 512; old_data_stripe_length = odata * chunk; -- -2.17.0 +2.17.1 |