integity -> integrity in comment for dm_table_get_integrity_disk Signed-off-by: Yonggil Song <yonggil.song@xxxxxxxxxxx> --- drivers/md/dm-table.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c index d8034ff0cb24..be0a9024923d 100644 --- a/drivers/md/dm-table.c +++ b/drivers/md/dm-table.c @@ -1151,7 +1151,7 @@ static struct gendisk * dm_table_get_integrity_disk(struct dm_table *t) * underlying devices have an integrity profile. But all devices may * not have matching profiles (checking all devices isn't reliable * during table load because this table may use other DM device(s) which - * must be resumed before they will have an initialized integity + * must be resumed before they will have an initialized integrity * profile). Consequently, stacked DM devices force a 2 stage integrity * profile validation: First pass during table load, final pass during * resume. -- 2.34.1 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
