From: Alan Cox <alan@linux.intel.com>
To: ian.campbell@citrix.com, linux-kernel@vger.kernel.org
Subject: [RESEND PATCH] xen: clean up event funcs
Date: Wed, 17 Feb 2010 12:57:32 +0000 [thread overview]
Message-ID: <20100217125723.15007.56854.stgit@localhost.localdomain> (raw)
mk_pirq_info, gsi_from_irq and vector_from_irq are static and unused in the
C file that defines them. Remove them and the warnings this causes.
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
drivers/xen/events.c | 27 ---------------------------
1 files changed, 0 insertions(+), 27 deletions(-)
diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index ce602dd..5131ef6 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -131,13 +131,6 @@ static struct irq_info mk_virq_info(unsigned short evtchn, unsigned short virq)
.cpu = 0, .u.virq = virq };
}
-static struct irq_info mk_pirq_info(unsigned short evtchn,
- unsigned short gsi, unsigned short vector)
-{
- return (struct irq_info) { .type = IRQT_PIRQ, .evtchn = evtchn,
- .cpu = 0, .u.pirq = { .gsi = gsi, .vector = vector } };
-}
-
/*
* Accessors for packed IRQ information.
*/
@@ -177,26 +170,6 @@ static unsigned virq_from_irq(unsigned irq)
return info->u.virq;
}
-static unsigned gsi_from_irq(unsigned irq)
-{
- struct irq_info *info = info_for_irq(irq);
-
- BUG_ON(info == NULL);
- BUG_ON(info->type != IRQT_PIRQ);
-
- return info->u.pirq.gsi;
-}
-
-static unsigned vector_from_irq(unsigned irq)
-{
- struct irq_info *info = info_for_irq(irq);
-
- BUG_ON(info == NULL);
- BUG_ON(info->type != IRQT_PIRQ);
-
- return info->u.pirq.vector;
-}
-
static enum xen_irq_type type_from_irq(unsigned irq)
{
return info_for_irq(irq)->type;
reply other threads:[~2010-02-17 13:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100217125723.15007.56854.stgit@localhost.localdomain \
--to=alan@linux.intel.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®