From: Scott Wood <scottwood@freescale.com>
To: Laurentiu Tudor <b10716@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Laurentiu Tudor <Laurentiu.Tudor@freescale.com>,
<kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] powerpc/e6500: add TMCFG0 register definition
Date: Thu, 24 Sep 2015 17:18:07 -0500 [thread overview]
Message-ID: <1443133087.32298.62.camel@freescale.com> (raw)
In-Reply-To: <5602BFEE.7060708@freescale.com>
On Wed, 2015-09-23 at 18:06 +0300, Laurentiu Tudor wrote:
> The register is not currently used in the base kernel
> but will be in a forthcoming kvm patch.
>
> Signed-off-by: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
> ---
> arch/powerpc/include/asm/reg_booke.h | 6 ++++++
> 1 file changed, 6 insertions(+)
Acked-by: Scott Wood <scottwood@freescale.com>
-Scott
next prev parent reply other threads:[~2015-09-24 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 15:06 [PATCH] powerpc/e6500: add TMCFG0 register definition Laurentiu Tudor
2015-09-24 22:18 ` Scott Wood [this message]
2015-10-15 5:29 ` Paul Mackerras
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=1443133087.32298.62.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Laurentiu.Tudor@freescale.com \
--cc=b10716@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).