Re: [PATCH] tile_edac: Fix the memory controller ID

[Mauro Carvalho Chehab]

Em 14-03-2012 16:11, Chris Metcalf escreveu:
> On 3/12/2012 10:02 AM, Mauro Carvalho Chehab wrote:
>> Fix a regression introduced by changeset 7b03829a8ba4:
>>
>> -       mci = edac_mc_alloc(sizeof(struct tile_edac_priv),
>> -               TILE_EDAC_NR_CSROWS, TILE_EDAC_NR_CHANS, pdev->id);
>> +       mci = edac_mc_alloc(0, ARRAY_SIZE(layers), layers, false,
>> +                           sizeof(struct tile_edac_priv));
>>
>> The pdev->id is missing.
>>
>> Compile-tested only. Btw, in order to compile it, I had to:
>>
>> 1) comment a header at arch/tile/include/asm/linkage.h:
>>
>> 	-#include <feedback.h>
>> 	+//#include <feedback.h>
>>
>> 2) Use the ./arch/tile/configs/tilegx_defconfig . the tilepro_defconfig
>>    is broken;
>>
>> 3) manually enable the EDAC module on it.
>>
>> Somebody has to fix it ;)
>>
>> Signed-off-by: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
> 
> You might amend the commit message based on our conversation, but otherwise:
> 
> Acked-by: Chris Metcalf <cmetcalf@xxxxxxxxxx>
> 
> Thanks for fixing up the tile EDAC driver, BTW :-)

Thanks for the ack!

Btw, I've introduced the bug, on this changeset:
	http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-edac.git;a=commit;h=3b6909be050f03366322b0d5b45d38eedee77574

So, it is my moral duty to fix it ;)

Btw, I'd appreciate if you could test the EDAC driver on tile after that
series. It makes the edac core more flexible to represent the location of
the broken memory on the way the memory controller works, in order to
put its fingers at the Field Repleaceable Unit (FRU) - like a DIMM stick.
It should be easy (and it probably makes sense on embedded hardware) to
add there a way to report each DRAM memory is broken.

The entire series is at:
	git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-edac.git hw_events_v7

Thank you!
Mauro

Thanks,
Mauro
> 

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