linux-kernel - [PATCH 0/2] Using function type to cleanup the function parament

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-next>] [day] [month] [year] [list]

Message-Id: <1436857153-18874-1-git-send-email-mhuang@redhat.com>
Date:	Tue, 14 Jul 2015 14:59:11 +0800
From:	Minfei Huang <mhuang@...hat.com>
To:	akpm@...ux-foundation.org, rob.jones@...ethink.co.uk,
	amhyung@...nel.org, rusty@...tcorp.com.au
Cc:	linux-kernel@...r.kernel.org, Minfei Huang <mnfhuang@...il.com>
Subject: [PATCH 0/2] Using function type to cleanup the function parament

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/