From: Tabi Timur-B04825 <B04825@freescale.com>
To: Wood Scott-B07421 <B07421@freescale.com>
Cc: "agraf@suse.de" <agraf@suse.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [linuxppc-release] [PATCH] KVM: PPC: e500: Don't hardcode PIR=0
Date: Fri, 02 Sep 2011 01:23:41 +0000 [thread overview]
Message-ID: <4E60301C.3070902@freescale.com> (raw)
In-Reply-To: <20110901230851.GA26220@schlenkerla.am.freescale.net>
Scott Wood wrote:
> Signed-off-by: Scott Wood<scottwood@freescale.com>
How about providing a better description?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Tabi Timur-B04825 <B04825@freescale.com>
To: Wood Scott-B07421 <B07421@freescale.com>
Cc: "agraf@suse.de" <agraf@suse.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: [linuxppc-release] [PATCH] KVM: PPC: e500: Don't hardcode PIR=0
Date: Fri, 2 Sep 2011 01:23:41 +0000 [thread overview]
Message-ID: <4E60301C.3070902@freescale.com> (raw)
In-Reply-To: <20110901230851.GA26220@schlenkerla.am.freescale.net>
Scott Wood wrote:
> Signed-off-by: Scott Wood<scottwood@freescale.com>
How about providing a better description?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-09-02 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 23:08 [PATCH] KVM: PPC: e500: Don't hardcode PIR=0 Scott Wood
2011-09-01 23:08 ` Scott Wood
2011-09-02 1:23 ` Tabi Timur-B04825 [this message]
2011-09-02 1:23 ` [linuxppc-release] " Tabi Timur-B04825
2011-09-02 15:12 ` Alexander Graf
2011-09-02 15:12 ` Alexander Graf
2011-09-02 18:14 ` Scott Wood
2011-09-02 18:14 ` Scott Wood
2011-09-02 19:23 ` Alexander Graf
2011-09-02 19:23 ` Alexander Graf
2011-09-02 19:35 ` Scott Wood
2011-09-02 19:35 ` Scott Wood
2011-09-02 19:46 ` Alexander Graf
2011-09-02 19:46 ` Alexander Graf
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=4E60301C.3070902@freescale.com \
--to=b04825@freescale.com \
--cc=B07421@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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.