Searched hist:"77 c5f5d2f212e1963063e427fc57c44bf6eae9fb" (Results 1 – 2 of 2) sorted by relevance
| /linux/drivers/edac/ |
| H A D | ghes_edac.c | 77c5f5d2f212e1963063e427fc57c44bf6eae9fb Fri Feb 15 10:11:57 CET 2013 Mauro Carvalho Chehab <mchehab@redhat.com> ghes_edac: Register at EDAC core the BIOS report
Register GHES at EDAC MC core, in order to avoid other
drivers to also handle errors and mangle with error data.
The edac core will warrant that just one driver will be used,
so the first one to register (BIOS first) will be the one that
will be reporting the hardware errors.
For now, the EDAC driver does nothing but to register at the
EDAC core, preventing the hardware-driven mechanism to
interfere with GHES.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
|
| /linux/ |
| H A D | MAINTAINERS | diff 77c5f5d2f212e1963063e427fc57c44bf6eae9fb Fri Feb 15 10:11:57 CET 2013 Mauro Carvalho Chehab <mchehab@redhat.com> ghes_edac: Register at EDAC core the BIOS report
Register GHES at EDAC MC core, in order to avoid other
drivers to also handle errors and mangle with error data.
The edac core will warrant that just one driver will be used,
so the first one to register (BIOS first) will be the one that
will be reporting the hardware errors.
For now, the EDAC driver does nothing but to register at the
EDAC core, preventing the hardware-driven mechanism to
interfere with GHES.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
|