linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Rabin Vincent <rabin@rab.in>,
	Abhijeet Dharmapurikar <adharmap@codeaurora.org>,
	Jean Delvare <khali@linux-fr.org>, Rajendra Nayak <rnayak@ti.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Vishwanath BS <vishwanath.bs@ti.com>,
	Partha Basak <p-basak2@ti.com>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-pm@lists.linux-foundation.org, linux-i2c@vger.kernel.org
Subject: Re: i2c runtime suspend and system wide suspend
Date: Thu, 30 Dec 2010 11:35:03 +0000	[thread overview]
Message-ID: <20101230113502.GA8537@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201012301149.30888.rjw@sisk.pl>

On Thu, Dec 30, 2010 at 11:49:30AM +0100, Rafael J. Wysocki wrote:
> On Thursday, December 30, 2010, Rabin Vincent wrote:

> > https://lists.linux-foundation.org/pipermail/linux-pm/2010-December/029658.html

> I'm not sure what happened to the last patch.  Is there a new version?
> If so, is it going to be pushed through the i2c tree, or should I take it?

Jean appears to be on holiday for the Christmas vacation.  I do have a
new version which I'll post later today.  Since it depends on the patch
protoyping the generic API calls which the SPI patch also depends on
it'd probably be best to merge via your tree.

      parent reply	other threads:[~2010-12-30 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30  4:39 i2c runtime suspend and system wide suspend Abhijeet Dharmapurikar
2010-12-30  6:32 ` Rabin Vincent
2010-12-30 10:49   ` Rafael J. Wysocki
2010-12-30 10:49     ` Rafael J. Wysocki
2010-12-30 11:35     ` Mark Brown [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=20101230113502.GA8537@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=adharmap@codeaurora.org \
    --cc=khali@linux-fr.org \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=p-basak2@ti.com \
    --cc=rabin@rab.in \
    --cc=rjw@sisk.pl \
    --cc=rnayak@ti.com \
    --cc=vishwanath.bs@ti.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).