From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: [patch 04/11] Add INIT_ARRAY() to kernel.h
Date: Tue, 18 Sep 2007 17:06:05 -0400 [thread overview]
Message-ID: <20070918210735.808225635@polymtl.ca> (raw)
In-Reply-To: 20070918210601.028313546@polymtl.ca
[-- Attachment #1: declare-array.patch --]
[-- Type: text/plain, Size: 967 bytes --]
Add initialization of an array, which needs brackets that would pollute kernel
code, to kernel.h. It is used to declare arguments passed as function parameters
such as:
text_poke(addr, INIT_ARRAY(unsigned char, 0xf0, len), len);
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
---
include/linux/kernel.h | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6-lttng/include/linux/kernel.h
===================================================================
--- linux-2.6-lttng.orig/include/linux/kernel.h 2007-09-18 10:09:15.000000000 -0400
+++ linux-2.6-lttng/include/linux/kernel.h 2007-09-18 13:12:34.000000000 -0400
@@ -400,4 +400,6 @@ struct sysinfo {
#define NUMA_BUILD 0
#endif
+#define INIT_ARRAY(type, val, len) ((type [len]){ [0 ... (len)-1] = (val) })
+
#endif
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-09-18 21:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:06 [patch 00/11] Text Edit Lock for 2.6.23-rc6-mm1 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 01/11] Kprobes - use a mutex to protect the instruction pages list Mathieu Desnoyers
2007-09-18 21:06 ` [patch 02/11] Kprobes - do not use kprobes mutex in arch code Mathieu Desnoyers
2007-09-18 21:06 ` [patch 03/11] Kprobes - declare kprobe_mutex static Mathieu Desnoyers
2007-09-18 21:06 ` Mathieu Desnoyers [this message]
2007-09-18 21:06 ` [patch 05/11] Text Edit Lock - Architecture Independent Code Mathieu Desnoyers
2007-09-18 21:06 ` [patch 06/11] Text Edit Lock - Alternative code for i386 and x86_64 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 07/11] Text Edit Lock - kprobes architecture independent support Mathieu Desnoyers
2007-09-18 21:06 ` [patch 08/11] Text Edit Lock - kprobes i386 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 09/11] Text Edit Lock - kprobes x86_64 Mathieu Desnoyers
2007-09-18 21:06 ` [patch 10/11] Text Edit Lock - i386 standardize debug rodata Mathieu Desnoyers
2007-09-18 21:06 ` [patch 11/11] Text Edit Lock - x86_64 " Mathieu Desnoyers
2007-09-20 23:10 ` [patch 00/11] Text Edit Lock for 2.6.23-rc6-mm1 Andrew Morton
2007-09-21 17:29 ` Christoph Hellwig
2007-09-21 18:11 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 2:02 [patch 00/11] Text Edit Lock for 2.6.24-rc4-git3 Mathieu Desnoyers
2007-12-06 2:02 ` [patch 04/11] Add INIT_ARRAY() to kernel.h Mathieu Desnoyers
2007-11-13 18:46 [patch 00/11] Text Edit Lock Mathieu Desnoyers
2007-11-13 18:46 ` [patch 04/11] Add INIT_ARRAY() to kernel.h Mathieu Desnoyers
2007-09-17 18:40 [patch 00/11] Text Edit Lock Mathieu Desnoyers
2007-09-17 18:40 ` [patch 04/11] Add INIT_ARRAY() to kernel.h Mathieu Desnoyers
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=20070918210735.808225635@polymtl.ca \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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