From: Chris Ball <cjb@laptop.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] mmc: core: add the debug message for SET_BLOCK_COUNT
Date: Sat, 11 Feb 2012 16:06:11 -0500 [thread overview]
Message-ID: <m2r4y1krlo.fsf@bob.laptop.org> (raw)
In-Reply-To: <4F30B2E6.60406@samsung.com> (Jaehoon Chung's message of "Tue, 07 Feb 2012 14:13:10 +0900")
Hi,
On Tue, Feb 07 2012, Jaehoon Chung wrote:
> This patch is added just debug message.
> Almost features need to use the CMD23.
> But we didn't see the debug message for sbc.
> If sbc's message can see, should be help for debugging.
> (We can check whether use the cmd23 or not)
>
> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> drivers/mmc/core/core.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 8a19143..6b72eb8 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -188,6 +188,12 @@ mmc_start_request(struct mmc_host *host, struct mmc_request *mrq)
> struct scatterlist *sg;
> #endif
>
> + if (mrq->sbc) {
> + pr_debug("<%s: starting CMD%u arg %08x flags %08x>\n",
> + mmc_hostname(host), mrq->sbc->opcode,
> + mrq->sbc->arg, mrq->sbc->flags);
> + }
> +
> pr_debug("%s: starting CMD%u arg %08x flags %08x\n",
> mmc_hostname(host), mrq->cmd->opcode,
> mrq->cmd->arg, mrq->cmd->flags);
Thanks, pushed to mmc-next for 3.4.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-02-11 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 5:13 [PATCH] mmc: core: add the debug message for SET_BLOCK_COUNT Jaehoon Chung
2012-02-07 7:27 ` Namjae Jeon
2012-02-08 7:40 ` Jaehoon Chung
2012-02-08 9:13 ` Namjae Jeon
2012-02-11 21:06 ` Chris Ball [this message]
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=m2r4y1krlo.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox