From: Thomas Gleixner <tglx@linutronix.de>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [PATCH] irq: Add EXPORT_SYMBOL to function of irq generic-chip
Date: Wed, 12 Oct 2011 11:25:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1110121036170.3240@ionos> (raw)
In-Reply-To: <1318403810-21860-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>
On Wed, 12 Oct 2011, Nobuhiro Iwamatsu wrote:
> Although some functions of of irq generic-chip can be used,
> since EXPORT_SYMBOL is not specified, it cannot use.
This does not make sense. In which context they can't be used?
> This is revised that EXPORT_SYMBOL can be added and referred
> to in functions.
EXPORT_SYMBOL_GPL if at all please.
And I'd rather avoid the exports, except those
> +EXPORT_SYMBOL(irq_alloc_generic_chip);
> +EXPORT_SYMBOL(irq_setup_generic_chip);
> +EXPORT_SYMBOL(irq_setup_alt_chip);
> +EXPORT_SYMBOL(irq_remove_generic_chip);
which are really necessary. To gain access to the various helper
functions we're better off to create a data structure with function
pointers.
struct irq_gc_functions {
void (* irq_gc_noop)(...);
...
};
Instantiate this structure in kernel/irq/generic-chip.c, statically
initialize it with pointers to those helper functions and export that
data structure. That's way more efficient than having the overhead of
the symbol export for each of the functions.
Thanks,
tglx
next prev parent reply other threads:[~2011-10-12 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 7:16 Nobuhiro Iwamatsu
2011-10-12 9:25 ` Thomas Gleixner [this message]
2011-10-13 2:50 ` Nobuhiro Iwamatsu
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=alpine.LFD.2.02.1110121036170.3240@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.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
all inboxes | Powered by JetHome®