Currently, the comment detailing the handle_stripe() function
is located above the analyse_stripe() function. Move this
comment above the handle_stripe() function instead, allowing
greater ease of comparison between the comment and the
actual function contents.
Signed-off-by: John Pittman <jpittman@xxxxxxxxxx>
---
drivers/md/raid5.c | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 4ce0d7502fad..9812dc1c709b 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -4342,20 +4342,6 @@ static void handle_stripe_expansion(struct r5conf *conf, struct stripe_head *sh)
async_tx_quiesce(&tx);
}
-/*
- * handle_stripe - do things to a stripe.
- *
- * We lock the stripe by setting STRIPE_ACTIVE and then examine the
- * state of various bits to see what needs to be done.
- * Possible results:
- * return some read requests which now have data
- * return some write requests which are safely on storage
- * schedule a read on some buffers
- * schedule a write of some buffers
- * return confirmation of parity correctness
- *
- */
-
static void analyse_stripe(struct stripe_head *sh, struct stripe_head_state *s)
{
struct r5conf *conf = sh->raid_conf;
@@ -4651,6 +4637,18 @@ static void break_stripe_batch_list(struct stripe_head *head_sh,
wake_up(&head_sh->raid_conf->wait_for_overlap);
}
+/*
+ * handle_stripe - do things to a stripe.
+ *
+ * We lock the stripe by setting STRIPE_ACTIVE and then examine the
+ * state of various bits to see what needs to be done.
+ * Possible results:
+ * return some read requests which now have data
+ * return some write requests which are safely on storage
+ * schedule a read on some buffers
+ * schedule a write of some buffers
+ * return confirmation of parity correctness
+ */
static void handle_stripe(struct stripe_head *sh)
{
struct stripe_head_state s;
--
2.17.1
