public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/1] Update CPER maintainership
Date: Tue,  6 Jan 2026 11:24:25 +0100	[thread overview]
Message-ID: <cover.1767694575.git.mchehab+huawei@kernel.org> (raw)

Hi Ard/Rafael,

This is a suggestion, so I'm marking it as a RFC.

At least on my eyes, and looking at the discussions on this thread:
    https://lore.kernel.org/all/20251222091334.5cb8465f@foz.lan/

It sounds to me that the better would be to have the code under cper*
maintained together with APEI code, as the main source of CPER records
is via APEI/GHES.

So, at least on my eyes, people maintaining and reviewing should be
the same - or a superset of what's currently there.

The patch on this series:

1. Add cper* files to APEI;
2. remove them from EFI - mostly to avoid having two maintainers for
   the same file.

Another option would be to do just (1), keeping the CPER files listed
on two maintainers' entries.

Comments?

Regards,
Mauro

Mauro Carvalho Chehab (1):
  MAINTAINERS: add cper to APEI files

 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

-- 
2.52.0


             reply	other threads:[~2026-01-06 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 10:24 Mauro Carvalho Chehab [this message]
2026-01-06 10:24 ` [PATCH RFC 1/1] MAINTAINERS: add cper to APEI files Mauro Carvalho Chehab
2026-01-08 12:52   ` Ard Biesheuvel

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=cover.1767694575.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=ardb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    /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