Subject: [merged] fsnotify-remove-pointless-null-initializers.patch removed from -mm tree
To: jack@xxxxxxx,eparis@xxxxxxxxxxxxxx,hch@xxxxxx,viro@xxxxxxxxxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Wed, 22 Jan 2014 12:11:29 -0800
The patch titled
Subject: fsnotify: remove pointless NULL initializers
has been removed from the -mm tree. Its filename was
fsnotify-remove-pointless-null-initializers.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Jan Kara <jack@xxxxxxx>
Subject: fsnotify: remove pointless NULL initializers
We usually rely on the fact that struct members not specified in the
initializer are set to NULL. So do that with fsnotify function pointers
as well.
Signed-off-by: Jan Kara <jack@xxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
Cc: Eric Paris <eparis@xxxxxxxxxxxxxx>
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/notify/dnotify/dnotify.c | 3 ---
fs/notify/fanotify/fanotify.c | 1 -
kernel/audit_tree.c | 2 --
kernel/audit_watch.c | 3 ---
4 files changed, 9 deletions(-)
diff -puN fs/notify/dnotify/dnotify.c~fsnotify-remove-pointless-null-initializers fs/notify/dnotify/dnotify.c
--- a/fs/notify/dnotify/dnotify.c~fsnotify-remove-pointless-null-initializers
+++ a/fs/notify/dnotify/dnotify.c
@@ -138,9 +138,6 @@ static void dnotify_free_mark(struct fsn
static struct fsnotify_ops dnotify_fsnotify_ops = {
.handle_event = dnotify_handle_event,
- .free_group_priv = NULL,
- .freeing_mark = NULL,
- .free_event = NULL,
};
/*
diff -puN fs/notify/fanotify/fanotify.c~fsnotify-remove-pointless-null-initializers fs/notify/fanotify/fanotify.c
--- a/fs/notify/fanotify/fanotify.c~fsnotify-remove-pointless-null-initializers
+++ a/fs/notify/fanotify/fanotify.c
@@ -230,5 +230,4 @@ const struct fsnotify_ops fanotify_fsnot
.handle_event = fanotify_handle_event,
.free_group_priv = fanotify_free_group_priv,
.free_event = fanotify_free_event,
- .freeing_mark = NULL,
};
diff -puN kernel/audit_tree.c~fsnotify-remove-pointless-null-initializers kernel/audit_tree.c
--- a/kernel/audit_tree.c~fsnotify-remove-pointless-null-initializers
+++ a/kernel/audit_tree.c
@@ -936,8 +936,6 @@ static void audit_tree_freeing_mark(stru
static const struct fsnotify_ops audit_tree_ops = {
.handle_event = audit_tree_handle_event,
- .free_group_priv = NULL,
- .free_event = NULL,
.freeing_mark = audit_tree_freeing_mark,
};
diff -puN kernel/audit_watch.c~fsnotify-remove-pointless-null-initializers kernel/audit_watch.c
--- a/kernel/audit_watch.c~fsnotify-remove-pointless-null-initializers
+++ a/kernel/audit_watch.c
@@ -505,9 +505,6 @@ static int audit_watch_handle_event(stru
static const struct fsnotify_ops audit_watch_fsnotify_ops = {
.handle_event = audit_watch_handle_event,
- .free_group_priv = NULL,
- .freeing_mark = NULL,
- .free_event = NULL,
};
static int __init audit_watch_init(void)
_
Patches currently in -mm which might be from jack@xxxxxxx are
origin.patch
fs-pipec-skip-file_update_time-on-frozen-fs.patch
rbtree-test-move-rb_node-to-the-middle-of-the-test-struct.patch
rbtree-test-test-rbtree_postorder_for_each_entry_safe.patch
net-netfilter-ipset-ip_set_hash_netifacec-use-rbtree-postorder-iteration-instead-of-opencoding.patch
fs-ubifs-use-rbtree-postorder-iteration-helper-instead-of-opencoding.patch
fs-ext4-use-rbtree-postorder-iteration-helper-instead-of-opencoding.patch
fs-jffs2-use-rbtree-postorder-iteration-helper-instead-of-opencoding.patch
fs-ext3-use-rbtree-postorder-iteration-helper-instead-of-opencoding.patch
fs-ext3-use-rbtree-postorder-iteration-helper-instead-of-opencoding-fix.patch
arch-sh-kernel-dwarfc-use-rbtree-postorder-iteration-helper-instead-of-solution-using-repeated-rb_erase.patch
userns-relax-the-posix_acl_valid-checks.patch
linux-next.patch
block-blk-mq-cpuc-use-hotcpu_notifier.patch
kernel-use-lockless-list-for-smp_call_function_single.patch
mm-add-strictlimit-knob-v2.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
