From: Ulf Hansson <ulf.hansson@linaro.org>
To: Markus Mayer <markus.mayer@linaro.org>
Cc: Chris Ball <chris@printf.net>, Tim Kryger <tim.kryger@gmail.com>,
Mike Looijmans <mike.looijmans@topic.nl>,
Andrew Bresticker <abrestic@chromium.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] mmc: sdhci: Use mmc core regulator infrastucture
Date: Fri, 13 Jun 2014 12:39:50 +0200 [thread overview]
Message-ID: <CAPDyKFo4pU4i+bvcLFNnQUaGpQDKfnnkYJki+B8mMQw99-HVWg@mail.gmail.com> (raw)
In-Reply-To: <1402598935-3701-1-git-send-email-markus.mayer@linaro.org>
On 12 June 2014 20:48, Markus Mayer <markus.mayer@linaro.org> wrote:
> This series switches the common SDHCI code over to use mmc_host's
> regulator pointers rather than keeping its own set.
>
> In addition, we can now re-use the newly introduced local "mmc" pointer
> in several other function calls in lieu of using host->mmc.
>
> The first patch in the series has been posted before
> (https://lkml.org/lkml/2014/4/24/947). The two follow-on patches have
> not. Patches 2 & 3 could be squashed together if the maintainers were
> so inclined.
Yes, please squash them. Otherwise this looks great!
Kind regards
Uffe
prev parent reply other threads:[~2014-06-13 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 18:48 [PATCH v3 0/3] mmc: sdhci: Use mmc core regulator infrastucture Markus Mayer
2014-06-12 18:48 ` [PATCH v3 1/3] " Markus Mayer
2014-06-12 18:48 ` [PATCH v3 2/3] mmc: sdhci: Use existing mmc pointer calling mmc_regulator_set_ocr() Markus Mayer
2014-06-12 18:48 ` [PATCH v3 3/3] mmc: sdhci: Replace host->mmc with mmc where possible Markus Mayer
2014-06-13 10:39 ` Ulf Hansson [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=CAPDyKFo4pU4i+bvcLFNnQUaGpQDKfnnkYJki+B8mMQw99-HVWg@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=abrestic@chromium.org \
--cc=chris@printf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=markus.mayer@linaro.org \
--cc=mike.looijmans@topic.nl \
--cc=tim.kryger@gmail.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;
as well as URLs for NNTP newsgroup(s).