From: Art Haas <ahaas@airmail.net>
To: Neil Brown <neilb@cse.unsw.edu.au>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: [PATCH] C99 initiailzers for xor.h
Date: Thu, 27 Feb 2003 15:38:19 -0600 [thread overview]
Message-ID: <20030227213819.GB8116@debian> (raw)
Hi.
This patch converts the file to use C99 initializers. It's against the
current BK.
Art Haas
===== include/asm-generic/xor.h 1.2 vs edited =====
--- 1.2/include/asm-generic/xor.h Mon Oct 21 03:13:10 2002
+++ edited/include/asm-generic/xor.h Thu Feb 27 10:27:14 2003
@@ -678,35 +678,35 @@
}
static struct xor_block_template xor_block_8regs = {
- name: "8regs",
- do_2: xor_8regs_2,
- do_3: xor_8regs_3,
- do_4: xor_8regs_4,
- do_5: xor_8regs_5,
+ .name = "8regs",
+ .do_2 = xor_8regs_2,
+ .do_3 = xor_8regs_3,
+ .do_4 = xor_8regs_4,
+ .do_5 = xor_8regs_5,
};
static struct xor_block_template xor_block_32regs = {
- name: "32regs",
- do_2: xor_32regs_2,
- do_3: xor_32regs_3,
- do_4: xor_32regs_4,
- do_5: xor_32regs_5,
+ .name = "32regs",
+ .do_2 = xor_32regs_2,
+ .do_3 = xor_32regs_3,
+ .do_4 = xor_32regs_4,
+ .do_5 = xor_32regs_5,
};
static struct xor_block_template xor_block_8regs_p = {
- name: "8regs_prefetch",
- do_2: xor_8regs_p_2,
- do_3: xor_8regs_p_3,
- do_4: xor_8regs_p_4,
- do_5: xor_8regs_p_5,
+ .name = "8regs_prefetch",
+ .do_2 = xor_8regs_p_2,
+ .do_3 = xor_8regs_p_3,
+ .do_4 = xor_8regs_p_4,
+ .do_5 = xor_8regs_p_5,
};
static struct xor_block_template xor_block_32regs_p = {
- name: "32regs_prefetch",
- do_2: xor_32regs_p_2,
- do_3: xor_32regs_p_3,
- do_4: xor_32regs_p_4,
- do_5: xor_32regs_p_5,
+ .name = "32regs_prefetch",
+ .do_2 = xor_32regs_p_2,
+ .do_3 = xor_32regs_p_3,
+ .do_4 = xor_32regs_p_4,
+ .do_5 = xor_32regs_p_5,
};
#define XOR_TRY_TEMPLATES \
--
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759
reply other threads:[~2003-02-27 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030227213819.GB8116@debian \
--to=ahaas@airmail.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).