From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] common/sched: Correct function prototypes
Date: Thu, 10 Oct 2013 19:25:32 +0100 [thread overview]
Message-ID: <CE7CAFAC.38F71%keir.xen@gmail.com> (raw)
In-Reply-To: <1381424754-7451-1-git-send-email-andrew.cooper3@citrix.com>
On 10/10/2013 18:05, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> struct vcpu pointers are traditionally v rather than d.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> George Dunlap <george.dunlap@eu.citrix.com>
Acked-by: Keir Fraser <keir@xen.org>
> ---
> xen/include/xen/sched.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
> index 1765e18..2e83f08 100644
> --- a/xen/include/xen/sched.h
> +++ b/xen/include/xen/sched.h
> @@ -567,9 +567,9 @@ void sched_set_node_affinity(struct domain *, nodemask_t
> *);
> int sched_id(void);
> void sched_tick_suspend(void);
> void sched_tick_resume(void);
> -void vcpu_wake(struct vcpu *d);
> -void vcpu_sleep_nosync(struct vcpu *d);
> -void vcpu_sleep_sync(struct vcpu *d);
> +void vcpu_wake(struct vcpu *v);
> +void vcpu_sleep_nosync(struct vcpu *v);
> +void vcpu_sleep_sync(struct vcpu *v);
>
> /*
> * Force synchronisation of given VCPU's state. If it is currently
> descheduled,
next prev parent reply other threads:[~2013-10-10 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 17:05 [PATCH] common/sched: Correct function prototypes Andrew Cooper
2013-10-10 18:25 ` Keir Fraser [this message]
2013-10-11 6:55 ` Jan Beulich
2013-10-11 9:40 ` Tim Deegan
2013-10-11 11:49 ` Jan Beulich
2013-10-11 12:06 ` Tim Deegan
2013-10-11 13:54 ` Keir Fraser
2013-10-11 14:47 ` George Dunlap
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=CE7CAFAC.38F71%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).