From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v3] xen: handle paged gfn in wrmsr_hypervisor_regs
Date: Fri, 03 May 2013 17:06:37 +0100 [thread overview]
Message-ID: <CDA99F1D.24013%keir.xen@gmail.com> (raw)
In-Reply-To: <5183FBD602000078000D339F@nat28.tlf.novell.com>
On 03/05/2013 17:03, "Jan Beulich" <JBeulich@suse.com> wrote:
>>> ... and here. If at all these ought to go into a separate patch
>>> (which we'd likely postpone until after 4.3).
>>
>> But they are errors?
>
> Right. But they weren't handled as such so far, and doing the
> conversion isn't the purpose of the patch.
Okay, I wasn't sure how dismissive your "if at all" was. :)
>> Could agree with postponing to post-4.3 though.
>
> Hence the request to split off that part of the patch. I'd be happy
> to apply that after the trees got branched.
Fine.
-- Keir
next prev parent reply other threads:[~2013-05-03 16:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 16:24 [PATCH] xen: handle paged gfn in wrmsr_hypervisor_regs Olaf Hering
2013-05-03 7:12 ` Jan Beulich
2013-05-03 12:58 ` Olaf Hering
2013-05-03 13:40 ` Olaf Hering
2013-05-03 13:53 ` Jan Beulich
2013-05-03 12:57 ` [PATCH v2] " Olaf Hering
2013-05-03 13:58 ` Jan Beulich
2013-05-03 14:11 ` Olaf Hering
2013-05-03 14:24 ` Jan Beulich
2013-05-03 14:26 ` Keir Fraser
2013-05-03 14:31 ` Jan Beulich
2013-05-03 15:19 ` Olaf Hering
2013-05-03 15:55 ` Keir Fraser
2013-05-03 15:17 ` [PATCH v3] " Olaf Hering
2013-05-03 15:30 ` Jan Beulich
2013-05-03 15:48 ` Olaf Hering
2013-05-03 15:53 ` Jan Beulich
2013-05-03 15:58 ` Keir Fraser
2013-05-03 16:03 ` Jan Beulich
2013-05-03 16:06 ` Keir Fraser [this message]
2013-05-03 15:55 ` Keir Fraser
2013-05-03 15:43 ` [PATCH v4] " Olaf Hering
2013-05-03 16:29 ` [PATCH v5] " Olaf Hering
2013-05-08 9:27 ` Jan Beulich
2013-05-08 10:51 ` Olaf Hering
2013-05-08 11:41 ` Jan Beulich
2013-05-08 11:45 ` Olaf Hering
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=CDA99F1D.24013%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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.