[PATCH 00/10] staging: lustre: cleanup up libcfs hash code for upstream

[James Simmons]

From: James Simmons <uja.ornl@xxxxxxxxx>

This patch brings the libcfs hash handling up to linux
kernel coding style. Various typedefs and macros have
been removed.

Signed-off-by: James Simmons <uja.ornl@xxxxxxxxx>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245
Reviewed-on: http://review.whamcloud.com/14624
Reviewed-by: Bob Glossman <bob.glossman@xxxxxxxxx>
Reviewed-by: frank zago <fzago@xxxxxxxx>
Reviewed-by: Oleg Drokin <oleg.drokin@xxxxxxxxx>

James Simmons (10):
  staging: lustre: change cfs_hash_lock_ops_t to struct
  staging: lustre: change cfs_hash_hlist_ops_t to struct
  staging: lustre: change cfs_hash_ops_t to struct
  staging: lustre: change cfs_hash_dhead*_t to struct
  staging: lustre: change cfs_hash_head*_t to struct
  staging: lustre: convert last typedef data types in hash.c
  staging: lustre: cleanup over 80 characters in libcfs_hash.h
  staging: lustre: remove white space in libcfs_hash.h
  staging: lustre: fix remaining checkpatch issues for libcfs_hash.h
  staging: lustre: remove white space in hash.c

 .../lustre/include/linux/libcfs/libcfs_hash.h      |  350 +++++++++-------
 drivers/staging/lustre/lustre/ldlm/ldlm_resource.c |   18 +-
 drivers/staging/lustre/lustre/libcfs/hash.c        |  447 ++++++++++----------
 drivers/staging/lustre/lustre/lov/lov_internal.h   |    2 +-
 drivers/staging/lustre/lustre/lov/lov_pool.c       |    6 +-
 drivers/staging/lustre/lustre/obdclass/cl_object.c |    6 +-
 drivers/staging/lustre/lustre/obdclass/lu_object.c |    6 +-
 .../staging/lustre/lustre/obdclass/obd_config.c    |    8 +-
 drivers/staging/lustre/lustre/osc/osc_quota.c      |    2 +-
 drivers/staging/lustre/lustre/ptlrpc/connection.c  |    8 +-
 10 files changed, 451 insertions(+), 402 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/