mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Thompson <davthompson@nvidia.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	Shravan Ramani <shravankr@nvidia.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: RE: [bug report] EDAC, mellanox: Add ECC support for BlueField DDR4
Date: Mon, 17 Mar 2025 21:34:05 +0000	[thread overview]
Message-ID: <PH7PR12MB59028CE9CE0034598F539BC7C7DF2@PH7PR12MB5902.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250311103106.GBZ9AQ6u6B8bd6W0Ul@fat_crate.local>

> -----Original Message-----
> From: Borislav Petkov <bp@alien8.de>
> Sent: Tuesday, March 11, 2025 6:31 AM
> To: David Thompson <davthompson@nvidia.com>
> Cc: Dan Carpenter <dan.carpenter@linaro.org>; Shravan Ramani
> <shravankr@nvidia.com>; linux-edac@vger.kernel.org; lkml <linux-
> kernel@vger.kernel.org>
> 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

  reply	other threads:[~2025-03-17 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <046bf689-9a2b-4993-b8ca-927d7d2a0cc5@stanley.mountain>
2025-03-03 14:52 ` Borislav Petkov
2025-03-11  2:22   ` David Thompson
2025-03-11  8:12     ` Dan Carpenter
2025-03-11 10:31     ` Borislav Petkov
2025-03-17 21:34       ` David Thompson [this message]
2025-03-18 23:42         ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH7PR12MB59028CE9CE0034598F539BC7C7DF2@PH7PR12MB5902.namprd12.prod.outlook.com \
    --to=davthompson@nvidia.com \
    --cc=bp@alien8.de \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shravankr@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®