From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Markus Reichl <m.reichl@fivetechno.de>,
Kukjin Kim <kgene@kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: exynos-5422-odroid: Remove always_on for eMMC and SD regulators
Date: Mon, 04 Apr 2016 09:37:05 +0900 [thread overview]
Message-ID: <5701B731.2030806@samsung.com> (raw)
In-Reply-To: <56FE898F.4050404@fivetechno.de>
On 01.04.2016 23:45, Markus Reichl wrote:
> Allow these suplies to be switched off if not used.
s/suplies/supplies/
>
> Signed-off-by: Markus Reichl <m.reichl@fivetechno.de>
> ---
> Tested with eMMC only on XU4.
> SD still needs testing.
I wanted to test your patches but the first does not apply
(next-20160401, my for-next) so I gave up.
I think this patch should be squashed with previous one. I don't see
benefits of splitting this (but maybe I am missing something?).
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-04-04 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 14:45 [PATCH] ARM: dts: exynos-5422-odroid: Remove always_on for eMMC and SD regulators Markus Reichl
2016-04-04 0:37 ` Krzysztof Kozlowski [this message]
2016-04-04 8:38 ` Markus Reichl
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=5701B731.2030806@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.reichl@fivetechno.de \
/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.