From: Art Haas <ahaas@neosoft.com>
To: linux-kernel@vger.kernel.org
Subject: C99 designated initializer patch for fs/romfs
Date: Sat, 28 Sep 2002 12:59:07 -0500 [thread overview]
Message-ID: <20020928175907.GE22783@debian> (raw)
Hi.
Here's a small patch for fixing fs/romfs/inode.c to C99 designated
initializers. Patch is against 2.5.39.
Art Haas
--- linux-2.5.39/fs/romfs/inode.c.old 2002-08-31 21:57:37.000000000 -0500
+++ linux-2.5.39/fs/romfs/inode.c 2002-09-28 10:36:22.000000000 -0500
@@ -456,16 +456,16 @@
/* Mapping from our types to the kernel */
static struct address_space_operations romfs_aops = {
- readpage: romfs_readpage
+ .readpage = romfs_readpage
};
static struct file_operations romfs_dir_operations = {
- read: generic_read_dir,
- readdir: romfs_readdir,
+ .read = generic_read_dir,
+ .readdir = romfs_readdir,
};
static struct inode_operations romfs_dir_inode_operations = {
- lookup: romfs_lookup,
+ .lookup = romfs_lookup,
};
static mode_t romfs_modemap[] =
@@ -590,10 +590,10 @@
}
static struct super_operations romfs_ops = {
- alloc_inode: romfs_alloc_inode,
- destroy_inode: romfs_destroy_inode,
- read_inode: romfs_read_inode,
- statfs: romfs_statfs,
+ .alloc_inode = romfs_alloc_inode,
+ .destroy_inode = romfs_destroy_inode,
+ .read_inode = romfs_read_inode,
+ .statfs = romfs_statfs,
};
static struct super_block *romfs_get_sb(struct file_system_type *fs_type,
@@ -603,11 +603,11 @@
}
static struct file_system_type romfs_fs_type = {
- owner: THIS_MODULE,
- name: "romfs",
- get_sb: romfs_get_sb,
- kill_sb: kill_block_super,
- fs_flags: FS_REQUIRES_DEV,
+ .owner = THIS_MODULE,
+ .name = "romfs",
+ .get_sb = romfs_get_sb,
+ .kill_sb = kill_block_super,
+ .fs_flags = FS_REQUIRES_DEV,
};
static int __init init_romfs_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:53 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=20020928175907.GE22783@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