All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework
Date: Fri, 19 Aug 2011 11:58:36 +0200	[thread overview]
Message-ID: <CACRpkdbAm5Z4NSZwtMSXSN9zzQW5p=zWmt1922oR1Sj2AbyZnw@mail.gmail.com> (raw)
In-Reply-To: <cover.1313664897.git.mika.westerberg@linux.intel.com>

On Thu, Aug 18, 2011 at 2:23 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:

> This is an updated series which should fix few races seen when aggressive
> clock gating is active. The first patch actually just renames the gating
> functions to make their use-cases a bit more clear.

Wow excellent work Mika, this is exactly how we should fix this.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Chris: you get to decide whether we push this for the -rc or -next,
since it fixes a regression for Mika I suggest this should go into -rc.

Thanks a *lot* Mika!
Linus Walleij

  parent reply	other threads:[~2011-08-19  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 12:23 [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework Mika Westerberg
2011-08-18 12:23 ` [PATCH v2 1/3] mmc: rename mmc_host_clk_{ungate|gate} to mmc_host_clk_{hold|release} Mika Westerberg
2011-08-18 12:23 ` [PATCH v2 2/3] mmc: prevent aggressive clock gating to race with ios updates Mika Westerberg
2011-08-18 12:23 ` [PATCH v2 3/3] mmc: use non-reentrant workqueue for clock gating Mika Westerberg
2011-08-19  9:58 ` Linus Walleij [this message]
2011-08-19 17:13 ` [PATCH v2 0/3] mmc: fixes for aggressive clock gating framework Chris Ball

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='CACRpkdbAm5Z4NSZwtMSXSN9zzQW5p=zWmt1922oR1Sj2AbyZnw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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 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.