From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Meng Xu <mengxu@cis.upenn.edu>,
Dario Faggioli <dfaggioli@suse.com>
Subject: [PATCH] sched/rt: Fix build after c/s c3715dd8fb766
Date: Thu, 8 Mar 2018 11:12:48 +0000 [thread overview]
Message-ID: <1520507568-10146-1-git-send-email-andrew.cooper3@citrix.com> (raw)
Travis reports:
sched_rt.c:241:30: error: unused function 'rt_dom' [-Werror,-Wunused-function]
static inline struct rt_dom *rt_dom(const struct domain *dom)
^
1 error generated.
when compiling with Clang. Drop the function.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: George Dunlap <george.dunlap@eu.citrix.com>
CC: Dario Faggioli <dfaggioli@suse.com>
CC: Meng Xu <mengxu@cis.upenn.edu>
---
xen/common/sched_rt.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/xen/common/sched_rt.c b/xen/common/sched_rt.c
index 1c72ea8..ac79f15 100644
--- a/xen/common/sched_rt.c
+++ b/xen/common/sched_rt.c
@@ -238,11 +238,6 @@ static inline struct rt_vcpu *rt_vcpu(const struct vcpu *vcpu)
return vcpu->sched_priv;
}
-static inline struct rt_dom *rt_dom(const struct domain *dom)
-{
- return dom->sched_priv;
-}
-
static inline struct list_head *rt_runq(const struct scheduler *ops)
{
return &rt_priv(ops)->runq;
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-03-08 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 11:12 Andrew Cooper [this message]
2018-03-08 16:58 ` [PATCH] sched/rt: Fix build after c/s c3715dd8fb766 George Dunlap
2018-03-08 18:16 ` Meng Xu
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=1520507568-10146-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dfaggioli@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=mengxu@cis.upenn.edu \
--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).