From: Minfei Huang <mhuang@redhat.com>
To: akpm@linux-foundation.org, rob.jones@codethink.co.uk,
amhyung@kernel.org, rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org, Minfei Huang <mnfhuang@gmail.com>
Subject: [PATCH 0/2] Using function type to cleanup the function parament
Date: Tue, 14 Jul 2015 14:59:11 +0800 [thread overview]
Message-ID: <1436857153-18874-1-git-send-email-mhuang@redhat.com> (raw)
From: Minfei Huang <mnfhuang@gmail.com>
This patchset do the cleanup. For now, we can use function type
as the parament to simplify the code.
Previously, we will declare the function as following:
bool each_symbol_section(bool (*fn)(const struct symsearch *arr,
struct module *owner,
void *data), void *data);
Once we define the function as a type, we can just declare the function
as following.
bool each_symbol_section(find_symbol_in_section_t fn, void *data);
Minfei Huang (2):
Define find_symbol_in_section_t as function type to simplify the code
Define kallsyms_cmp_symbol_t as function type to simplify the code
include/linux/kallsyms.h | 10 +++-------
include/linux/module.h | 19 +++++++++----------
kernel/kallsyms.c | 4 +---
kernel/module.c | 13 +++----------
4 files changed, 16 insertions(+), 30 deletions(-)
--
2.2.2
next reply other threads:[~2015-07-14 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 6:59 Minfei Huang [this message]
2015-07-14 6:59 ` [PATCH 1/2] Define find_symbol_in_section_t as function type to simplify the code Minfei Huang
2015-07-14 7:04 ` Minfei Huang
2015-07-14 21:52 ` Rusty Russell
2015-07-15 2:11 ` Minfei Huang
2015-07-15 20:31 ` Andrew Morton
2015-07-16 11:29 ` Rusty Russell
2015-07-14 6:59 ` [PATCH 2/2] Define kallsyms_cmp_symbol_t " Minfei Huang
2015-07-14 7:05 ` Minfei Huang
2015-07-14 7:06 ` [PATCH 0/2] Using function type to cleanup the function parament Minfei Huang
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=1436857153-18874-1-git-send-email-mhuang@redhat.com \
--to=mhuang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnfhuang@gmail.com \
--cc=rob.jones@codethink.co.uk \
--cc=rusty@rustcorp.com.au \
/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®