linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Maya Erez <merez@codeaurora.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Lee Susman <lsusman@codeaurora.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] block: Add eMMC4.5 packed commands unit-tests
Date: Tue, 12 Jun 2012 10:11:16 -0400	[thread overview]
Message-ID: <x491ulkk4cb.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1339494088-29126-2-git-send-email-merez@codeaurora.org> (Maya Erez's message of "Tue, 12 Jun 2012 12:41:28 +0300")

Maya Erez <merez@codeaurora.org> writes:

> Expose the following packed commands tests:
> - Test the write packed commands list preparation
> - Simulate a returned error code
> - Send an invalid packed command to the card
>
> Signed-off-by: Lee Susman <lsusman@codeaurora.org>
> Signed-off-by: Maya Erez <merez@codeaurora.org>
>
> diff --git a/drivers/mmc/card/Kconfig b/drivers/mmc/card/Kconfig
> index 3b1f783..bbe8cac 100644
> --- a/drivers/mmc/card/Kconfig
> +++ b/drivers/mmc/card/Kconfig
> @@ -67,3 +67,14 @@ config MMC_TEST
>  
>  	  This driver is only of interest to those developing or
>  	  testing a host driver. Most people should say N here.
> +
> +config MMC_BLOCK_TEST
> +	tristate "MMC block test"
> +	depends on MMC_BLOCK && IOSCHED_TEST

Umm, if this depends on your iosched-test patch, then you should make
them both part of a patch series.  It would have answered one of my
questions on that patch.

Cheers,
Jeff

  reply	other threads:[~2012-06-12 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  9:41 [PATCH 0/1] block: Add eMMC4.5 packed commands unit-tests Maya Erez
2012-06-12  9:41 ` [PATCH 1/1] " Maya Erez
2012-06-12 14:11   ` Jeff Moyer [this message]
2012-06-12 20:04     ` merez

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=x491ulkk4cb.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lsusman@codeaurora.org \
    --cc=merez@codeaurora.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;
as well as URLs for NNTP newsgroup(s).