Usually there are multiple mmc host controllers, rename mmc queue thread
by host index, so we can easily identify which controller it belongs to

Signed-off-by: Ethan Du <ethan....@gmail.com>
---
 drivers/mmc/card/queue.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/drivers/mmc/card/queue.c b/drivers/mmc/card/queue.c
index e876678..673bbdb 100644
--- a/drivers/mmc/card/queue.c
+++ b/drivers/mmc/card/queue.c
@@ -211,7 +211,8 @@ int mmc_init_queue(struct mmc_queue *mq, struct
mmc_card *card, spinlock_t *lock

        init_MUTEX(&mq->thread_sem);

-       mq->thread = kthread_run(mmc_queue_thread, mq, "mmcqd");
+       mq->thread = kthread_run(mmc_queue_thread, mq, "mmcqd/%d",
+               host->index);
        if (IS_ERR(mq->thread)) {
                ret = PTR_ERR(mq->thread);
                goto free_bounce_sg;
-- 
1.5.6.5
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to