From: Minfei Huang <mnfhuang@gmail.com>
To: Minfei Huang <mhuang@redhat.com>
Cc: akpm@linux-foundation.org, rob.jones@codethink.co.uk,
amhyung@kernel.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Using function type to cleanup the function parament
Date: Tue, 14 Jul 2015 15:06:16 +0800 [thread overview]
Message-ID: <20150714070616.GC26166@dhcp-128-51.nay.redhat.com> (raw)
In-Reply-To: <1436857153-18874-1-git-send-email-mhuang@redhat.com>
Lost the character 'n' in the Namhyung Kim <namhyung@kernel.org>.
Resent it.
On 07/14/15 at 02:59P, Minfei Huang wrote:
> 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
>
prev parent reply other threads:[~2015-07-14 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 6:59 [PATCH 0/2] Using function type to cleanup the function parament Minfei Huang
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 ` Minfei Huang [this message]
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=20150714070616.GC26166@dhcp-128-51.nay.redhat.com \
--to=mnfhuang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=amhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.