RE: [bug report] EDAC, mellanox: Add ECC support for BlueField DDR4

[David Thompson]

> -----Original Message-----
> From: Borislav Petkov <bp@xxxxxxxxx>
> Sent: Tuesday, March 11, 2025 6:31 AM
> To: David Thompson <davthompson@xxxxxxxxxx>
> Cc: Dan Carpenter <dan.carpenter@xxxxxxxxxx>; Shravan Ramani
> <shravankr@xxxxxxxxxx>; linux-edac@xxxxxxxxxxxxxxx; lkml <linux-
> kernel@xxxxxxxxxxxxxxx>
> Subject: Re: [bug report] EDAC, mellanox: Add ECC support for BlueField DDR4
> 
> On Tue, Mar 11, 2025 at 02:22:20AM +0000, David Thompson wrote:
> > Shravan and I will investigate solving this 'smatch' warning.
> 
> Thanks, sounds like you're still interested in this driver.
> 
> Which means, I'd need either of you to be responsive on the ML and review when
> patches like that get sent. Otherwise, I'll simply orphan the thing and it'll bitrot
> until it gets removed completely.
> 
> So, if interested, which email address should be in MAINTAINERS so that it gets
> CCed? Shravan's or yours or both or some ML you guys want to be CCed?
> 

Shravan's email is currently listed in MAINTAINERS for bluefield_edac.c
My email address can be added there as well.  Shall I post a patch to do this?

> > I setup a recent linux-next repo, installed the sparse package, and
> > downloaded + built the smatch tool.
> 
> Btw, you don't really need linux-next - you can follow EDAC development by
> fetching the edac-for-next branch from this repo here:
> 
> https://web.git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
> 
> That's what goes into linux-next too and EDAC patches should be based on that
> branch.

Ok, will do future work out of the "ras" repo, edac-for-next branch.

> 
> Holler if there are questions.
> 
> Thx.
> 
> --
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette