All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Piotr Sroka <piotrs@cadence.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [v4 1/3] mmc: sdhci-cadence: Fix writing PHY delay
Date: Tue, 21 Mar 2017 16:39:45 +0900	[thread overview]
Message-ID: <CAK7LNATGQsoQTgNq_MqksF_+EZ27+iUuh+7VTXQWX50ba98LfQ@mail.gmail.com> (raw)
In-Reply-To: <1490008372-16372-1-git-send-email-piotrs@cadence.com>

Hi Piotr,

2017-03-20 20:12 GMT+09:00 Piotr Sroka <piotrs@cadence.com>:
> Add polling for ACK to be sure that data are written to PHY register.
>
> Signed-off-by: Piotr Sroka <piotrs@cadence.com>


Reviewed-by: Masahiro Yamada <yamada.masahiro@socionext.com>



One you get Acked-by or Reviewed-by,
please make sure to add it in the next version.


I issued my Reviewed-by multiple times
(because maintainers usually pick up the latest version).




-- 
Best Regards
Masahiro Yamada

      parent reply	other threads:[~2017-03-21  7:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 11:12 [v4 1/3] mmc: sdhci-cadence: Fix writing PHY delay Piotr Sroka
2017-03-20 11:12 ` Piotr Sroka
2017-03-20 11:20 ` [v4 2/3] dt-bindings: mmc: add description of PHY delays for sdhci-cadence Piotr Sroka
2017-03-20 11:20   ` Piotr Sroka
2017-03-21  7:40   ` Masahiro Yamada
2017-03-20 11:20 ` [v4 3/3] mmc: sdhci-cadence: Update PHY delay configuration Piotr Sroka
2017-03-20 11:20   ` Piotr Sroka
2017-03-21  1:45   ` Masahiro Yamada
2017-03-21  7:01     ` Piotr Sroka
2017-03-21  7:01       ` Piotr Sroka
2017-03-21  7:32       ` Masahiro Yamada
2017-03-22  7:08         ` Piotr Sroka
2017-03-22  7:24           ` Masahiro Yamada
2017-03-21  7:39 ` Masahiro Yamada [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=CAK7LNATGQsoQTgNq_MqksF_+EZ27+iUuh+7VTXQWX50ba98LfQ@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=piotrs@cadence.com \
    --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.