From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, <xen-devel@lists.xensource.com>,
<konrad.wilk@oracle.com>, <david.vrabel@citrix.com>,
<boris.ostrovsky@oracle.com>, <tglx@linutronix.de>,
<mingo@redhat.com>, <hpa@zytor.com>, <mmarek@suse.cz>,
<linux-kbuild@vger.kernel.org>
Subject: Re: [Xen-devel] [RESEND Patch V2 0/4] xen: auto-generate symbols for xen hypercalls
Date: Mon, 2 Mar 2015 11:00:06 +0000 [thread overview]
Message-ID: <54F442B6.1050400@citrix.com> (raw)
In-Reply-To: <1421826565-10826-1-git-send-email-jgross@suse.com>
On 21/01/15 07:49, Juergen Gross wrote:
> The Xen hypercalls are defined in include/xen/interface/xen.h. There
> are some places where for each hypercall a table element is created.
> Instead of manually add each hypercall element to these tables use
> an auto generated header built during the make process of the kernel.
Applied to devel/for-linus-4.1, thanks.
David
prev parent reply other threads:[~2015-03-02 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 7:49 [RESEND Patch V2 0/4] xen: auto-generate symbols for xen hypercalls Juergen Gross
2015-01-21 7:49 ` [RESEND Patch V2 1/4] xen: build infrastructure for generating hypercall depending symbols Juergen Gross
2015-01-28 5:11 ` Juergen Gross
2015-02-06 15:00 ` Juergen Gross
2015-02-19 0:00 ` Ingo Molnar
2015-02-13 5:33 ` Juergen Gross
2015-02-18 23:59 ` Ingo Molnar
2015-01-21 7:49 ` [RESEND Patch V2 2/4] xen: synchronize include/xen/interface/xen.h with xen Juergen Gross
2015-01-21 7:49 ` [RESEND Patch V2 3/4] xen: use generated hypervisor symbols in arch/x86/xen/trace.c Juergen Gross
2015-01-21 7:49 ` [RESEND Patch V2 4/4] xen: use generated hypercall symbols in arch/x86/xen/xen-head.S Juergen Gross
2015-03-02 11:00 ` David Vrabel [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=54F442B6.1050400@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox