From: He Chen <he.chen@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Lai <paul.c.lai@intel.com>, Feng Wu <feng.wu@intel.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v6] xen/sm{e, a}p: allow disabling sm{e, a}p for Xen itself
Date: Tue, 20 Sep 2016 15:26:13 +0800 [thread overview]
Message-ID: <20160920072613.GA2301@HE> (raw)
In-Reply-To: <57E0F90C02000078001106FB@prv-mh.provo.novell.com>
On Tue, Sep 20, 2016 at 12:53:32AM -0600, Jan Beulich wrote:
> >>> On 20.09.16 at 04:29, <he.chen@linux.intel.com> wrote:
> > Sorry for the late response, I saw the this patch was merged but soon
> > got reverted, and the revert message says this patch is still buggy.
> >
> > I would be most grateful if you would point out the buggy part of this
> > patch and the reason why revert it.
>
> Well, I've already told you on the 5th - see
> https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg00414.html
> suggesting that you never tested the patch on older hardware.
> Additionally you could (and perhaps should) have looked yourself
> immediately at the failed smoke test logs (they may have got purged
> by now), referenced from the respective osstest mail
> https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg00411.html
Oops, I didn't receive your reply at 5th Sep due to our mail server
temporarily down that day, terribly sorry..
Thank you for replying again and I will cook a patch and test it asap...
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-09-20 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 5:17 [PATCH v6] xen/sm{e, a}p: allow disabling sm{e, a}p for Xen itself He Chen
2016-09-05 10:06 ` Jan Beulich
2016-09-05 13:07 ` Jan Beulich
2016-09-20 2:29 ` He Chen
2016-09-20 6:53 ` Jan Beulich
2016-09-20 7:26 ` He Chen [this message]
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=20160920072613.GA2301@HE \
--to=he.chen@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=feng.wu@intel.com \
--cc=paul.c.lai@intel.com \
--cc=xen-devel@lists.xenproject.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.