linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/6] mmc: sdhi: add basic r8a7795 support
Date: Fri, 22 Jan 2016 11:26:21 +0000	[thread overview]
Message-ID: <56A211DD.6050009@de.bosch.com> (raw)
In-Reply-To: <1453220461-2598-1-git-send-email-wsa@the-dreams.de>

Hi Wolfram,

On 19.01.2016 17:20, Wolfram Sang wrote:
> So, I started working on the SDHI part. Since Dirk seems to be working on the
> clocks already (thanks!), I evaluated the patches for the mmc-subsystem and
> refactored the subset which gets the basic functionality run. A few cleanups
> were applied, too. The patches are RFC because I want to check one more issue
> (restore clock settings after software reset) and also I need to do Gen2
> regression testing. However, release early, I wanted to show you what I am
> hacking on here.


I've looked over it and from my limited knowledge point of view it looks 
good. Thanks!

I'd say that patches 2/6 and 4/6 are mainly independent on r8a7795 
support and could be sent without RFC.

I'm not sure if my knowledge is enough to give an Acked-by or 
Reviewed-by, though ;)

Best regards

Dirk


  parent reply	other threads:[~2016-01-22 11:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 16:20 [RFC 0/6] mmc: sdhi: add basic r8a7795 support Wolfram Sang
2016-01-19 16:56 ` Dirk Behme
2016-01-22  8:54 ` Wolfram Sang
2016-01-22 10:32 ` Yoshihiro Shimoda
2016-01-22 11:26 ` Dirk Behme [this message]
2016-01-22 11:30 ` Dirk Behme
2016-01-22 11:36 ` Dirk Behme
2016-01-22 21:30 ` Wolfram Sang
2016-01-25  8:51 ` Yoshihiro Shimoda
2016-01-25  9:08 ` Dirk Behme
2016-01-25 16:25 ` Dirk Behme
2016-01-25 19:24 ` Wolfram Sang
2016-01-25 20:47 ` Geert Uytterhoeven
2016-01-26  6:12 ` Dirk Behme
2016-01-26  8:34 ` Wolfram Sang

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=56A211DD.6050009@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --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).