From: Milton Miller <miltonm@bga.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/4] irq: remove unnecessary __ref on irq_alloc_descs
Date: Wed, 25 May 2011 01:34:18 -0500 [thread overview]
Message-ID: <irq-alloc-no-longer-needs-ref@mdm.bga.com> (raw)
In-Reply-To: <generic-irq-changes@mdm.bga.com>
febcb0c59a (irq: Remove unnecessary bootmem code) removed the
slab_is_available() conditonal call to alloc_bootmem* but missed
removeing the __ref annotation.
Signed-off-by: Milton Miller <miltonm@bga.com>
Index: work.git/kernel/irq/irqdesc.c
===================================================================
--- work.git.orig/kernel/irq/irqdesc.c 2011-05-23 14:29:22.960588100 -0500
+++ work.git/kernel/irq/irqdesc.c 2011-05-23 14:29:27.377586564 -0500
@@ -351,8 +351,7 @@ EXPORT_SYMBOL_GPL(irq_free_descs);
*
* Returns the first irq number or error code
*/
-int __ref
-irq_alloc_descs(int irq, unsigned int from, unsigned int cnt, int node)
+int irq_alloc_descs(int irq, unsigned int from, unsigned int cnt, int node)
{
int start, ret;
next prev parent reply other threads:[~2011-05-25 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <generic-irq-changes@mdm.bga.com>
2011-05-25 6:34 ` [PATCH 1/4] sparse irq: protect irq_to_desc against irq_free_descs Milton Miller
2011-05-25 8:14 ` Thomas Gleixner
2011-05-25 10:49 ` Milton Miller
2011-05-25 10:54 ` Thomas Gleixner
2011-05-25 6:34 ` [PATCH 2/4] irq: radix_tree_insert can fail Milton Miller
2011-05-25 8:18 ` Thomas Gleixner
2011-05-25 10:48 ` Milton Miller
2011-05-25 6:34 ` Milton Miller [this message]
2011-05-25 6:34 ` [PATCH RFC 4/4] irq: allow a per-allocation upper limit when allocating irqs Milton Miller
2011-05-25 7:55 ` Ingo Molnar
2011-05-25 8:32 ` Thomas Gleixner
2011-05-27 3:38 ` Grant Likely
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=irq-alloc-no-longer-needs-ref@mdm.bga.com \
--to=miltonm@bga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).