Linux EDAC development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"John Snow" <jsnow@redhat.com>,
	qemu-devel@nongnu.org,
	"Richard Henderson" <richard.henderson@linaro.org>,
	linux-edac@vger.kernel.org, "Alex Williamson" <alex@shazbot.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"zhenwei pi" <zhenwei.pi@linux.dev>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Lukas Straub" <lukasstraub2@web.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Remove linux-edac
Date: Tue, 7 Jul 2026 09:51:19 +0200	[thread overview]
Message-ID: <20260707095119.4d1107af@foz.lan> (raw)
In-Reply-To: <20260703152529.GBakfUaQdmKSLZfqrt@fat_crate.local>

Hi Boris,

On Fri, 3 Jul 2026 08:25:29 -0700
Borislav Petkov <bp@alien8.de> wrote:

> On Tue, Jun 30, 2026 at 12:21:54PM -0700, Borislav Petkov wrote:
> > On Tue, Jun 30, 2026 at 09:27:32AM +0100, Daniel P. Berrangé wrote:  
> > > > Why is this thread CCing linux-edac?
> > > > 
> > > > I don't see any relation here...  
> > > 
> > > The linux-edac list was recently added to the QEMU MAINTAINERS
> > > file:
> > > 
> > >   https://gitlab.com/qemu-project/qemu/-/commit/4c5e70b9a42744401fc10b17cc61820586ba4a13
> > > 
> > > and the entry matches the qapi/acpi-hest.json file that John has
> > > modified, so gets auto-CC'd.
> > > 
> > > Admittedly the content in this series is not especially relevant
> > > to the liunux-edac list in this case, but the patch submission
> > > tools are just following the declared MAINTAINERS file entry.  
> > 
> > Thanks for letting me know.
> > 
> > @Mauro, please remove a linux-kernel mailing list from being CCed with qemu
> > patches. This is only going to cause a huuuge confusion as it is already
> > showing.

I was in vacations, so I only noticed this patch today.

We use linux-edac for userspace at least since Rasdaemon beginning,
so it was never a kernel-only ML. What happened in practice on the
recent times is that rasdaemon patches are usually pushed as PR
requests at github. Yet, still today, it is recommended to also
submit them to linux-edac ML:

	https://github.com/mchehab/rasdaemon#submitting-patches

Yet, I agree that having a separate ML for userspace RAS tools
makes sense. I'll check on a separate thread if we can create
one such list at vger.

> > 
> > Please do a separate list only for qemu RAS stuff. 

Instead of adding a patch removing it, better to wait for the ML 
creation and then apply a QEMU patch changing it, and another one
to rasdaemon.

Regards,
Mauro

> 
> ---
> 
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Fri, 3 Jul 2026 08:19:53 -0700
> Subject: [PATCH] MAINTAINERS: Remove linux-edac
> 
> The commit
> 
>   4c5e70b9a427 ("MAINTAINERS: update HEST maintainership entries")
> 
> added a linux kernel mailing list (linux-edac) which gets CCed
> automatically with qemu patches. This is absolutely confusing and it
> should not happen. Qemu should have its own ras mailing list where stuff
> like that goes.
> 
> Drop that list.
> 
> Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Cc: Markus Armbruster <armbru@redhat.com>
> Cc: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 97dcc78ded61..3664c0d67677 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2274,7 +2274,6 @@ F: docs/devel/testing/acpi-bits.rst
>  
>  ACPI/HEST/GHES
>  M: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> -L: linux-edac@vger.kernel.org
>  L: qemu-arm@nongnu.org
>  S: Maintained
>  F: hw/acpi/ghes.c



Thanks,
Mauro

      reply	other threads:[~2026-07-07  7:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 21:36 [PATCH 00/14] qapi: convert to explicit intro section syntax John Snow
2026-06-29 21:36 ` [PATCH 01/14] qapi: convert intro sections for error.json John Snow
2026-06-29 21:36 ` [PATCH 02/14] qapi: convert intro sections for acpi-hest.json John Snow
2026-06-29 21:36 ` [PATCH 03/14] qapi: convert intro sections for ebpf.json John Snow
2026-06-29 21:36 ` [PATCH 04/14] qapi: convert intro sections for uefi.json John Snow
2026-06-29 21:36 ` [PATCH 05/14] qapi: convert intro sections for compat.json John Snow
2026-06-29 21:36 ` [PATCH 06/14] qapi: convert intro sections for vfio.json John Snow
2026-06-29 21:36 ` [PATCH 07/14] qapi: convert intro sections for trace.json John Snow
2026-06-29 21:36 ` [PATCH 08/14] qapi: convert intro sections for misc-arm.json John Snow
2026-06-29 21:36 ` [PATCH 09/14] qapi: convert intro sections for cryptodev.json John Snow
2026-06-29 21:36 ` [PATCH 10/14] qapi: convert intro sections for machine-common.json John Snow
2026-06-29 21:36 ` [PATCH 11/14] qapi: convert intro sections for accelerator.json John Snow
2026-06-29 21:36 ` [PATCH 12/14] qapi: convert intro sections for authz.json John Snow
2026-06-29 21:36 ` [PATCH 13/14] qapi: convert intro sections for yank.json John Snow
2026-06-29 21:59   ` Lukas Straub
2026-06-29 21:36 ` [PATCH 14/14] qapi: convert intro sections for replay.json John Snow
2026-06-29 23:07 ` [PATCH 00/14] qapi: convert to explicit intro section syntax Borislav Petkov
2026-06-30  8:27   ` Daniel P. Berrangé
2026-06-30 19:21     ` Borislav Petkov
2026-07-03 15:25       ` [PATCH] MAINTAINERS: Remove linux-edac Borislav Petkov
2026-07-07  7:51         ` Mauro Carvalho Chehab [this message]

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=20260707095119.4d1107af@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=alex.bennee@linaro.org \
    --cc=alex@shazbot.org \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bp@alien8.de \
    --cc=clg@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=lukasstraub2@web.de \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=philmd@mailo.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=zhao1.liu@intel.com \
    --cc=zhenwei.pi@linux.dev \
    /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