From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, cjb@laptop.org,
linux-mmc@vger.kernel.org, g.liakhovetski@gmail.com
Subject: Re: [PATCH] mmc: sh_mmcif: Get rid of MMC_BLOCK dependency
Date: Thu, 10 Oct 2013 07:24:33 +0000 [thread overview]
Message-ID: <20131010072431.GA24126@verge.net.au> (raw)
In-Reply-To: <20131009224545.23119.45781.sendpatchset@w520>
On Thu, Oct 10, 2013 at 07:45:45AM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> It seems like sh_mmcif.c now is the only MMC driver depending on MMC_BLOCK,
> the hardware is not special in any way so rework the Kconfig dependency to
> be less special.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
>
> drivers/mmc/host/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 0001/drivers/mmc/host/Kconfig
> +++ work/drivers/mmc/host/Kconfig 2013-10-08 18:03:17.000000000 +0900
> @@ -588,7 +588,7 @@ config MMC_DW_PCI
>
> config MMC_SH_MMCIF
> tristate "SuperH Internal MMCIF support"
> - depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
> + depends on SUPERH || ARCH_SHMOBILE
> help
> This selects the MMC Host Interface controller (MMCIF).
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-10-10 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 22:45 [PATCH] mmc: sh_mmcif: Get rid of MMC_BLOCK dependency Magnus Damm
2013-10-10 7:24 ` Simon Horman [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=20131010072431.GA24126@verge.net.au \
--to=horms@verge.net.au \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).