All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
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 14:45:54 +0200	[thread overview]
Message-ID: <1736383.oJDPHdJZPn@avalon> (raw)
In-Reply-To: <1396353706-31864-1-git-send-email-ben.dooks@codethink.co.uk>

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>

-- 
Regards,

Laurent Pinchart


WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
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 12:45:54 +0000	[thread overview]
Message-ID: <1736383.oJDPHdJZPn@avalon> (raw)
In-Reply-To: <1396353706-31864-1-git-send-email-ben.dooks@codethink.co.uk>

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>

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-04-01 12:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 12:01 sh mmcif cleanups Ben Dooks
2014-04-01 12:01 ` 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   ` 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   ` 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   ` 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   ` 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   ` Ben Dooks
2014-04-01 12:01 ` [PATCH v2 6/6] mmc: sh-mmcif: final error path cleanup Ben Dooks
2014-04-01 12:01   ` Ben Dooks
2014-04-01 12:45 ` Laurent Pinchart [this message]
2014-04-01 12:45   ` sh mmcif cleanups Laurent Pinchart
2014-04-01 21:13   ` Ben Dooks
2014-04-01 21:13     ` Ben Dooks

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=1736383.oJDPHdJZPn@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=chris@printf.net \
    --cc=g.liakhovetski@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.