From: Ian Campbell <ian.campbell@citrix.com>
To: George Dunlap <dunlapg@umich.edu>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.6] x86/gdt: Drop write-only, xalloc()'d array from set_gdt()
Date: Wed, 5 Aug 2015 10:58:20 +0100 [thread overview]
Message-ID: <1438768700.9747.40.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZb_vof11O1fXz-Otjz7FkqW25t6H1o=Q_FJSSEKPREYcA@mail.gmail.com>
On Tue, 2015-08-04 at 15:17 +0100, George Dunlap wrote:
> On Mon, Aug 3, 2015 at 6:05 PM, Andrew Cooper <andrew.cooper3@citrix.com>
> wrote:
> > It is not used, and can cause a spurious failure of the set_gdt()
> > hypercall in
> > low memory situations.
> >
> > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
It's unclear from MAINTAINERS if this is formally enough for the patch to
be applied but under the circumstances (pretty obvious patch, Reviewed-by
more than one person, including the X86 MEMORY MANAGEMENT maintainer even
if mm.c isn't strictly under that for some reason) I've added my own
Revieed-by and applied, hopefully that is ok.
Perhaps there should be a patch to MAINTAINERS to add arch/x86/mm.c to the
relevant subsection? (Or maybe the file is just horribly named?)
Ian.
next prev parent reply other threads:[~2015-08-05 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 17:05 [PATCH for-4.6] x86/gdt: Drop write-only, xalloc()'d array from set_gdt() Andrew Cooper
2015-08-04 9:34 ` Wei Liu
2015-08-04 13:59 ` Ian Campbell
2015-08-04 14:05 ` Andrew Cooper
2015-08-05 10:57 ` Tim Deegan
2015-08-11 15:53 ` Jan Beulich
2015-08-04 14:17 ` George Dunlap
2015-08-05 9:58 ` Ian Campbell [this message]
2015-08-11 15:56 ` Jan Beulich
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=1438768700.9747.40.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dunlapg@umich.edu \
--cc=wei.liu2@citrix.com \
--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.