[PATCH 0/6] Add a per-dimm structure

From: Mauro Carvalho Chehab
Date: Wed Mar 07 2012 - 06:40:44 EST


Prepare the internal structures to represent the memory properties per dimm,
instead of per csrow.

This is needed for modern controllers with more than 2 channels, as the memories
at the same slot number but on different channels (or channel pairs) may be
different.

Mauro Carvalho Chehab (6):
edac: Create a dimm struct and move the labels into it
edac: Add per dimm's sysfs nodes
edac: move dimm properties to struct memset_info
edac: Don't initialize csrow's first_page & friends when not needed
edac: move nr_pages to dimm struct
edac: Add per-dimm sysfs show nodes

drivers/edac/amd64_edac.c | 73 +++--------
drivers/edac/amd76x_edac.c | 14 ++-
drivers/edac/cell_edac.c | 18 ++-
drivers/edac/cpc925_edac.c | 70 ++++++-----
drivers/edac/e752x_edac.c | 48 ++++---
drivers/edac/e7xxx_edac.c | 49 ++++---
drivers/edac/edac_mc.c | 97 ++++++++++-----
drivers/edac/edac_mc_sysfs.c | 269 +++++++++++++++++++++++++++++++++++++---
drivers/edac/i3000_edac.c | 24 ++--
drivers/edac/i3200_edac.c | 24 ++--
drivers/edac/i5000_edac.c | 31 ++---
drivers/edac/i5100_edac.c | 56 ++++++---
drivers/edac/i5400_edac.c | 38 ++----
drivers/edac/i7300_edac.c | 40 +++----
drivers/edac/i7core_edac.c | 41 +++----
drivers/edac/i82443bxgx_edac.c | 15 ++-
drivers/edac/i82860_edac.c | 13 ++-
drivers/edac/i82875p_edac.c | 22 +++-
drivers/edac/i82975x_edac.c | 28 +++--
drivers/edac/mpc85xx_edac.c | 16 ++-
drivers/edac/mv64x60_edac.c | 22 ++--
drivers/edac/pasemi_edac.c | 24 ++--
drivers/edac/ppc4xx_edac.c | 25 ++--
drivers/edac/r82600_edac.c | 13 ++-
drivers/edac/sb_edac.c | 39 +++---
drivers/edac/tile_edac.c | 17 ++--
drivers/edac/x38_edac.c | 24 ++--
include/linux/edac.h | 139 +++++++++++++++------
28 files changed, 808 insertions(+), 481 deletions(-)

--
1.7.8

--
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/