From: Timur Tabi <timur@freescale.com>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: agraf@suse.de, kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [linuxppc-release] [PATCH v11 6/8] PPC: select EPAPR_PARAVIRT for all users of epapr hcalls
Date: Fri, 22 Jun 2012 20:05:30 +0000 [thread overview]
Message-ID: <4FE4D00A.1000404@freescale.com> (raw)
In-Reply-To: <1340395478-19131-1-git-send-email-stuart.yoder@freescale.com>
Stuart Yoder wrote:
> -new in v11-- this patch is needed so the dependencies are correct
> for all users of epapr hcalls, without it there will be build issues
> after hardcoded opcodes for hcalls are removed
This should have been part of the patch description.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: <agraf@suse.de>, <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [linuxppc-release] [PATCH v11 6/8] PPC: select EPAPR_PARAVIRT for all users of epapr hcalls
Date: Fri, 22 Jun 2012 15:05:30 -0500 [thread overview]
Message-ID: <4FE4D00A.1000404@freescale.com> (raw)
In-Reply-To: <1340395478-19131-1-git-send-email-stuart.yoder@freescale.com>
Stuart Yoder wrote:
> -new in v11-- this patch is needed so the dependencies are correct
> for all users of epapr hcalls, without it there will be build issues
> after hardcoded opcodes for hcalls are removed
This should have been part of the patch description.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-06-22 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 20:04 [PATCH v11 6/8] PPC: select EPAPR_PARAVIRT for all users of epapr hcalls Stuart Yoder
2012-06-22 20:04 ` Stuart Yoder
2012-06-22 20:05 ` Timur Tabi [this message]
2012-06-22 20:05 ` [linuxppc-release] " Timur Tabi
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=4FE4D00A.1000404@freescale.com \
--to=timur@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=stuart.yoder@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 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.