From: Stephen Warren <swarren@wwwdotorg.org>
To: Hiroshi Doyu <hdoyu@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] memory: tegra30: Fix warning w/o PM_SLEEP
Date: Mon, 26 Nov 2012 12:33:58 -0700 [thread overview]
Message-ID: <50B3C426.4020605@wwwdotorg.org> (raw)
In-Reply-To: <1353501740-25420-1-git-send-email-hdoyu@nvidia.com>
On 11/21/2012 05:42 AM, Hiroshi Doyu wrote:
> Fix build warning w/o PM_SLEEP.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
I assume Greg will take this through his tree.
> Change-Id: I713f7dd697f1ad9fb1fee56b389b0d6c45bb540c
But that shouldn't be there though...
next prev parent reply other threads:[~2012-11-26 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 12:42 [PATCH 1/1] memory: tegra30: Fix warning w/o PM_SLEEP Hiroshi Doyu
2012-11-21 12:47 ` Hiroshi Doyu
2012-11-22 6:45 ` Stephen Warren
2012-11-26 19:33 ` Stephen Warren [this message]
2012-11-26 23:47 ` Greg Kroah-Hartman
2012-11-27 6:48 ` Hiroshi Doyu
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=50B3C426.4020605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=axel.lin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdoyu@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@nvidia.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