From: Art Haas <ahaas@neosoft.com>
To: linux-kernel@vger.kernel.org
Subject: C99 designated initializer patch for fs/ramfs
Date: Sat, 28 Sep 2002 12:54:21 -0500 [thread overview]
Message-ID: <20020928175421.GB22783@debian> (raw)
Hi.
Here's another small patch for converting fs/ramfs/inode.c to use
C99 designated initializers. The patch is against 2.5.39.
Art Haas
--- linux-2.5.39/fs/ramfs/inode.c.old 2002-09-16 09:34:08.000000000 -0500
+++ linux-2.5.39/fs/ramfs/inode.c 2002-09-28 10:36:22.000000000 -0500
@@ -276,35 +276,35 @@
}
static struct address_space_operations ramfs_aops = {
- readpage: ramfs_readpage,
- writepage: fail_writepage,
- prepare_write: ramfs_prepare_write,
- commit_write: ramfs_commit_write
+ .readpage = ramfs_readpage,
+ .writepage = fail_writepage,
+ .prepare_write = ramfs_prepare_write,
+ .commit_write = ramfs_commit_write
};
static struct file_operations ramfs_file_operations = {
- read: generic_file_read,
- write: generic_file_write,
- mmap: generic_file_mmap,
- fsync: ramfs_sync_file,
- sendfile: generic_file_sendfile,
+ .read = generic_file_read,
+ .write = generic_file_write,
+ .mmap = generic_file_mmap,
+ .fsync = ramfs_sync_file,
+ .sendfile = generic_file_sendfile,
};
static struct inode_operations ramfs_dir_inode_operations = {
- create: ramfs_create,
- lookup: simple_lookup,
- link: ramfs_link,
- unlink: ramfs_unlink,
- symlink: ramfs_symlink,
- mkdir: ramfs_mkdir,
- rmdir: ramfs_rmdir,
- mknod: ramfs_mknod,
- rename: ramfs_rename,
+ .create = ramfs_create,
+ .lookup = simple_lookup,
+ .link = ramfs_link,
+ .unlink = ramfs_unlink,
+ .symlink = ramfs_symlink,
+ .mkdir = ramfs_mkdir,
+ .rmdir = ramfs_rmdir,
+ .mknod = ramfs_mknod,
+ .rename = ramfs_rename,
};
static struct super_operations ramfs_ops = {
- statfs: simple_statfs,
- drop_inode: generic_delete_inode,
+ .statfs = simple_statfs,
+ .drop_inode = generic_delete_inode,
};
static int ramfs_fill_super(struct super_block * sb, void * data, int silent)
@@ -342,14 +342,14 @@
}
static struct file_system_type ramfs_fs_type = {
- name: "ramfs",
- get_sb: ramfs_get_sb,
- kill_sb: kill_litter_super,
+ .name = "ramfs",
+ .get_sb = ramfs_get_sb,
+ .kill_sb = kill_litter_super,
};
static struct file_system_type rootfs_fs_type = {
- name: "rootfs",
- get_sb: rootfs_get_sb,
- kill_sb: kill_litter_super,
+ .name = "rootfs",
+ .get_sb = rootfs_get_sb,
+ .kill_sb = kill_litter_super,
};
static int __init init_ramfs_fs(void)
--
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:[~2002-09-28 17:49 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=20020928175421.GB22783@debian \
--to=ahaas@neosoft.com \
--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