The patch titled
xfs: remove unused behaviour lock
has been added to the -mm tree. Its filename is
xfs-remove-unused-behaviour-lock.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: xfs: remove unused behaviour lock
From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
Also shrink XFS vnode as a side effect.
Signed-off-by: Alexey Dobriyan <adobriyan@xxxxxxxxx>
Cc: Nathan Scott <nathans@xxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
fs/xfs/xfs_behavior.h | 3 ---
1 files changed, 3 deletions(-)
diff -puN fs/xfs/xfs_behavior.h~xfs-remove-unused-behaviour-lock fs/xfs/xfs_behavior.h
--- 25/fs/xfs/xfs_behavior.h~xfs-remove-unused-behaviour-lock Tue Jun 20 15:45:35 2006
+++ 25-akpm/fs/xfs/xfs_behavior.h Tue Jun 20 15:45:35 2006
@@ -78,15 +78,12 @@
*
*/
-struct bhv_head_lock;
-
/*
* Behavior head. Head of the chain of behaviors.
* Contained within each virtualized object data structure.
*/
typedef struct bhv_head {
struct bhv_desc *bh_first; /* first behavior in chain */
- struct bhv_head_lock *bh_lockp; /* pointer to lock info struct */
} bhv_head_t;
/*
_
Patches currently in -mm which might be from adobriyan@xxxxxxxxx are
origin.patch
git-acpi.patch
git-block.patch
git-ieee1394.patch
git-libata-all.patch
git-mtd.patch
git-nfs.patch
xfs-remove-dir-check-in-xfs_link.patch
xfs-use-container_of-in-vn_from_inode.patch
xfs-pass-inode-to-xfs_ioc_space.patch
xfs-remove-unused-behaviour-lock.patch
x86-dont-trigger-full-rebuild-via-config_mtrr.patch
dont-trigger-full-rebuild-via-config_x86_mce.patch
remove-config_parport_arc-drivers-parport-parport_arcc.patch
two-additions-to-linux-documentation-ioctl-numbertxt.patch
more-bug_on-conversion.patch
emu10k1-mark-midi_spinlock-as-used.patch
nbd-endian-annotations.patch
documentation-ioctl-messtxt-start-tree-wide-ioctl-registry.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
