From: Chris Ball <cjb@laptop.org>
To: Ethan Du <ethan.too@gmail.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: name mmc queue thread by host index
Date: Thu, 30 Sep 2010 23:40:36 +0100 [thread overview]
Message-ID: <20100930224036.GA29160@void.printf.net> (raw)
In-Reply-To: <AANLkTikNzqe4ppJhGWapSwvXbpqABAjybOevwRds1Ou+@mail.gmail.com>
Hi Ethan,
On Mon, Sep 27, 2010 at 10:22:20AM +0800, Ethan Du wrote:
> 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.too@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
Thanks, applied to mmc-next. (This patch was line-wrapped; please
fix that next time.)
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-09-30 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 2:22 [PATCH] mmc: name mmc queue thread by host index Ethan Du
2010-09-30 22:40 ` Chris Ball [this message]
[not found] <AANLkTi=4mAFOZAMqg6oFs0ry9X8vxYh9ZU_Wz-Y+q9W6@mail.gmail.com>
2010-09-30 0:22 ` [PATCH] MMC: " Ethan Du
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100930224036.GA29160@void.printf.net \
--to=cjb@laptop.org \
--cc=ethan.too@gmail.com \
--cc=linux-mmc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.