From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/2] sh: fix SD / MMC configuration dependencies on
Date: Sat, 16 Apr 2011 00:37:13 +0000 [thread overview]
Message-ID: <20110416003713.GA25864@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.1104152000450.18593@axis700.grange>
On Fri, Apr 15, 2011 at 08:03:17PM +0200, Guennadi Liakhovetski wrote:
> Update CONFIG_MMC_TMIO to the new CONFIG_MMC_SDHI symbol and fix
> MMCIF to also function in modular builds for ecovec.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> Cc: Simon Horman <horms@verge.net.au>
> Cc: Magnus Damm <damm@opensource.se>
Acked-by: Simon Horman <horms@verge.net.au>
It is curious that these config options are only used by ecovec.
Is it because SDHI support is unconditional on other platforms - eg ap4evb?
next prev parent reply other threads:[~2011-04-16 0:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 18:18 [PATCH] i2c: add a module alias to the sh-mobile driver Guennadi Liakhovetski
2011-04-15 18:17 ` [PATCH] ALSA: add a module alias to the FSI driver Guennadi Liakhovetski
2011-04-15 18:04 ` [PATCH 2/2] sh: update SDHI configuration symbols in defconfigs Guennadi Liakhovetski
2011-04-15 18:03 ` [PATCH 1/2] sh: fix SD / MMC configuration dependencies on ecovec Guennadi Liakhovetski
2011-04-16 0:37 ` Simon Horman [this message]
2011-04-18 6:43 ` Guennadi Liakhovetski
2011-04-18 7:56 ` [PATCH 1/2] sh: fix SD / MMC configuration dependencies on Simon Horman
2011-04-18 9:48 ` [PATCH 1/2] sh: fix SD / MMC configuration dependencies on ecovec Paul Mundt
2011-04-16 0:38 ` [PATCH 2/2] sh: update SDHI configuration symbols in defconfigs Simon Horman
2011-04-18 6:49 ` Guennadi Liakhovetski
2011-04-18 8:16 ` Simon Horman
2011-04-18 8:24 ` [PATCH] ALSA: add a module alias to the FSI driver Simon Horman
2011-04-18 8:55 ` Liam Girdwood
2011-04-18 16:15 ` Mark Brown
2011-04-18 8:25 ` [PATCH] i2c: add a module alias to the sh-mobile driver Simon Horman
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=20110416003713.GA25864@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).