From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wang Dongsheng-B40534 <B40534@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Li Yang-R58472 <r58472@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Zhao Chenhui-B35336 <B35336@freescale.com>
Subject: Re: [RFC 2/2] powerpc/cputable: add wait feature for CPU kernel features
Date: Wed, 10 Jul 2013 19:33:21 +1000 [thread overview]
Message-ID: <1373448801.19894.17.camel@pasglop> (raw)
In-Reply-To: <ABB05CD9C9F68C46A5CEDC7F15439259FBEBFC@039-SN2MPN1-022.039d.mgd.msft.net>
On Wed, 2013-07-10 at 09:29 +0000, Wang Dongsheng-B40534 wrote:
> >
> Yes, the wait instructions is for cpu idle, It will be make cpu into
> low power mode, like DOZE & NAP. Each thread have this.
I don't need you to tell me by email, I need you to put a proper
comment in the patch submission so it ends up in the repository
and if possible a bit more detailed than that.
Ben.
next prev parent reply other threads:[~2013-07-10 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373444876-7783-1-git-send-email-dongsheng.wang@freescale.com>
[not found] ` <1373444876-7783-2-git-send-email-dongsheng.wang@freescale.com>
[not found] ` <1373448151.19894.16.camel@pasglop>
2013-07-10 9:29 ` [RFC 2/2] powerpc/cputable: add wait feature for CPU kernel features Wang Dongsheng-B40534
2013-07-10 9:33 ` Benjamin Herrenschmidt [this message]
2013-07-10 9:47 ` Wang Dongsheng-B40534
[not found] ` <1375118838.30721.43@snotra>
2013-07-30 3:30 ` Wang Dongsheng-B40534
[not found] ` <1375118509.30721.42@snotra>
2013-07-30 5:27 ` [RFC 1/2] fsl/pm: combined the idle(PH&PW) state Wang Dongsheng-B40534
2013-07-10 8:31 Dongsheng Wang
2013-07-10 8:31 ` [RFC 2/2] powerpc/cputable: add wait feature for CPU kernel features Dongsheng Wang
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=1373448801.19894.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B07421@freescale.com \
--cc=B35336@freescale.com \
--cc=B40534@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.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).