From: Jaehoon Chung <jh80.chung@samsung.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: "'Mark Brown'" <broonie@kernel.org>,
"'Liam Girdwood'" <lgirdwood@gmail.com>,
"'Chris Ball'" <cjb@laptop.org>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org,
"'Mark Brown'" <broonie@linaro.org>
Subject: Re: [PATCH 4/5] mmc: dw_mmc: Indicate that regulators may be absent
Date: Wed, 31 Jul 2013 12:29:27 +0900 [thread overview]
Message-ID: <51F88497.5020909@samsung.com> (raw)
In-Reply-To: <003901ce8d29$610ab3f0$23201bd0$%jun@samsung.com>
Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
Best Regards,
Jaehoon Chung
On 07/30/2013 10:33 PM, Seungwon Jeon wrote:
> On Tue, July 30, 2013, Mark Brown wrote:
>> From: Mark Brown <broonie@linaro.org>
>>
>> Use regulator_get_optional() to tell the core that requests for regulators
>> can fail in a real system.
>>
>> Signed-off-by: Mark Brown <broonie@linaro.org>
> Acked-by: Seungwon Jeon <tgih.jun@samsung.com>
>
> Thanks,
> Seungwon Jeon
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-07-31 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 11:46 [PATCH 1/5] regulator: core: Provide hints to the core about optional supplies Mark Brown
2013-07-30 11:46 ` [PATCH 2/5] mmc: core: Indicate that vmmcq may be absent Mark Brown
2013-07-30 11:46 ` [PATCH 3/5] mmc: sdhci: Indicate that regulators " Mark Brown
2013-07-30 11:46 ` [PATCH 4/5] mmc: dw_mmc: " Mark Brown
2013-07-30 13:33 ` Seungwon Jeon
2013-07-31 3:29 ` Jaehoon Chung [this message]
2013-07-30 11:46 ` [PATCH 5/5] mmc: pxamci: " Mark Brown
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=51F88497.5020909@samsung.com \
--to=jh80.chung@samsung.com \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=cjb@laptop.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
/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