lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Jul 2015 15:06:16 +0800
From:	Minfei Huang <mnfhuang@...il.com>
To:	Minfei Huang <mhuang@...hat.com>
Cc:	akpm@...ux-foundation.org, rob.jones@...ethink.co.uk,
	amhyung@...nel.org, rusty@...tcorp.com.au,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Using function type to cleanup the function parament

Lost the character 'n' in the Namhyung Kim <namhyung@...nel.org>.
Resent it.

On 07/14/15 at 02:59P, Minfei Huang wrote:
> From: Minfei Huang <mnfhuang@...il.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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ