All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: clarify idle vs sleep states
Date: Wed, 26 Sep 2012 10:57:40 -0600	[thread overview]
Message-ID: <50633404.6030400@wwwdotorg.org> (raw)
In-Reply-To: <1348664464-12079-1-git-send-email-linus.walleij@stericsson.com>

On 09/26/2012 07:01 AM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> This pure documentation fix tries to align the "idle" and
> "sleep" pin states to the idle and suspend states from
> runtime PM.

Seems reasonable,
Acked-by: Stephen Warren <swarren@nvidia.com>

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Stephen Warren <swarren@nvidia.com>,
	Anmar Oueja <anmar.oueja@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: clarify idle vs sleep states
Date: Wed, 26 Sep 2012 10:57:40 -0600	[thread overview]
Message-ID: <50633404.6030400@wwwdotorg.org> (raw)
In-Reply-To: <1348664464-12079-1-git-send-email-linus.walleij@stericsson.com>

On 09/26/2012 07:01 AM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> This pure documentation fix tries to align the "idle" and
> "sleep" pin states to the idle and suspend states from
> runtime PM.

Seems reasonable,
Acked-by: Stephen Warren <swarren@nvidia.com>

  reply	other threads:[~2012-09-26 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 13:01 [PATCH] pinctrl: clarify idle vs sleep states Linus Walleij
2012-09-26 13:01 ` Linus Walleij
2012-09-26 16:57 ` Stephen Warren [this message]
2012-09-26 16:57   ` Stephen Warren

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=50633404.6030400@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.