From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH] x86/CPUID: RSTR_FP_ERR_PTRS depends on FPU
Date: Mon, 9 Dec 2019 15:00:38 +0100 [thread overview]
Message-ID: <4ba450a8-50ed-892f-9b3f-d48282d9b40d@suse.com> (raw)
In-Reply-To: <40b7acd2-e98d-d744-6cea-0add8b19b74a@suse.com>
On 09.12.19 14:06, Jan Beulich wrote:
> On 26.09.2019 17:23, Jürgen Groß wrote:
>> On 25.09.19 17:27, Jan Beulich wrote:
>>> There's nothing to restore here if there's no FPU in the first place.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>
>> Release-acked-by: Juergen Gross <jgross@suse.com>
>
> While I've committed the change to the unstable branch, making use of
> this R-a-b now without asking would seem abusive to me. I'd expect
> you don't want the 4.13 branch disturbed more than really helpful,
> and hence I expect you'd rather not see this go in there now. Please
> let me know if you view this differently.
I appreciate that a lot. Please don't commit this to 4.13 now. :-)
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-09 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 15:27 [Xen-devel] [PATCH] x86/CPUID: RSTR_FP_ERR_PTRS depends on FPU Jan Beulich
2019-09-26 15:23 ` Jürgen Groß
2019-12-09 13:06 ` Jan Beulich
2019-12-09 14:00 ` Jürgen Groß [this message]
2019-10-08 9:32 ` [Xen-devel] Ping: " Jan Beulich
2019-12-06 18:48 ` Andrew Cooper
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=4ba450a8-50ed-892f-9b3f-d48282d9b40d@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--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.