linux-kernel - [PATCH 0/6] Post EDAC core fix patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1331122278-28458-1-git-send-email-mchehab@redhat.com>
Date:	Wed,  7 Mar 2012 09:11:12 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/6] Post EDAC core fix patches

Addresses some other stuff that requires cleaning, fixes or improvements after 
applying the proper support for FB-DIMM and for the modern Intel DDR2/DDR3 
memory controllers changeset.

Mauro Carvalho Chehab (6):
  edac: Initialize the dimm label with the known information
  edac_mc_sysfs: don't create inactive errcount sysfs nodes
  i5000_edac: Fix the logic that retrieves memory information
  edac: add a sysfs node that stores the max possible memory location
  edac: Call the sysfs nodes as "rank" instead of "dimm" if chip select
    is used
  i5400_edac: improve debug messages to better represent the filled
    memory

 drivers/edac/edac_mc.c       |   21 +++++-
 drivers/edac/edac_mc_sysfs.c |  147 +++++++++++++++++++++++++++++------------
 drivers/edac/i5000_edac.c    |  150 ++++++++++++++++++++++--------------------
 drivers/edac/i5400_edac.c    |   15 ++++-
 4 files changed, 216 insertions(+), 117 deletions(-)

-- 
1.7.8

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