From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Chris Ball <chris@printf.net>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
magnus.damm@opensource.se, linux-kernel@lists.codethink.co.uk
Subject: Re: sh mmcif cleanups
Date: Tue, 01 Apr 2014 21:13:09 +0000 [thread overview]
Message-ID: <533B2BE5.7060503@codethink.co.uk> (raw)
In-Reply-To: <1736383.oJDPHdJZPn@avalon>
On 01/04/14 13:45, Laurent Pinchart wrote:
> On Tuesday 01 April 2014 13:01:40 Ben Dooks wrote:
>> This is a second round of the mmcif cleanups
>>
>> Changes since v1:
>>
>> - fix issues with devm_ioremap return, and error printing
>> - change the initial print
>> - fix issue with disabling clock
>
> For the whole series,
>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks, guess this is too late for the current merge window now.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2014-04-01 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 12:01 sh mmcif cleanups Ben Dooks
2014-04-01 12:01 ` [PATCH v2 1/6] mmc: sh-mmcif: update to print version and bus clock rate on probe Ben Dooks
2014-04-01 12:01 ` [PATCH v2 2/6] mmc: sh-mmcif: use devm_ for ioremap Ben Dooks
2014-04-01 12:01 ` [PATCH v2 3/6] mmc: sh-mmcif: use devm_ for clock management Ben Dooks
2014-04-01 12:01 ` [PATCH v2 4/6] mmc: sh-mmcif: use devm_ for irq management Ben Dooks
2014-04-01 12:01 ` [PATCH v2 5/6] mmc: sh-mmcif: no need to call pm_runtime_suspend on error Ben Dooks
2014-04-01 12:01 ` [PATCH v2 6/6] mmc: sh-mmcif: final error path cleanup Ben Dooks
2014-04-01 12:45 ` sh mmcif cleanups Laurent Pinchart
2014-04-01 21:13 ` Ben Dooks [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=533B2BE5.7060503@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=chris@printf.net \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@opensource.se \
--cc=ulf.hansson@linaro.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).