bcache: fix indentation issue, remove tabs on a hunk of code

There is a hunk of code that is indented one level too deep, fix this
by removing the extra tabs.

Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Coly Li <colyli@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
index 4dee119c36646a54a301aafa280bc3d9a6df27e5..a697a3a923cd24638dd538ca2c3a110e1ff98ec1 100644 (file)
--- a/drivers/md/bcache/super.c
+++ b/drivers/md/bcache/super.c
@@ -1615,21 +1615,21 @@ static void conditional_stop_bcache_device(struct cache_set *c,
                 */
                pr_warn("stop_when_cache_set_failed of %s is \"auto\" and cache is dirty, stop it to avoid potential data corruption.",
                        d->disk->disk_name);
-                       /*
-                        * There might be a small time gap that cache set is
-                        * released but bcache device is not. Inside this time
-                        * gap, regular I/O requests will directly go into
-                        * backing device as no cache set attached to. This
-                        * behavior may also introduce potential inconsistence
-                        * data in writeback mode while cache is dirty.
-                        * Therefore before calling bcache_device_stop() due
-                        * to a broken cache device, dc->io_disable should be
-                        * explicitly set to true.
-                        */
-                       dc->io_disable = true;
-                       /* make others know io_disable is true earlier */
-                       smp_mb();
-                       bcache_device_stop(d);
+               /*
+                * There might be a small time gap that cache set is
+                * released but bcache device is not. Inside this time
+                * gap, regular I/O requests will directly go into
+                * backing device as no cache set attached to. This
+                * behavior may also introduce potential inconsistence
+                * data in writeback mode while cache is dirty.
+                * Therefore before calling bcache_device_stop() due
+                * to a broken cache device, dc->io_disable should be
+                * explicitly set to true.
+                */
+               dc->io_disable = true;
+               /* make others know io_disable is true earlier */
+               smp_mb();
+               bcache_device_stop(d);
        } else {
                /*
                 * dc->stop_when_cache_set_failed == BCH_CACHED_STOP_AUTO