RFC Update CPER maintainership
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 patch 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | MAINTAINERS: add cper to APEI filesMAINTAINERS | +2 | 1 reply |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Ard Biesheuvel |
|---|---|
| 1/1 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH RFC 0/1] Update CPER maintainership
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/[email protected]/
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(+)
Signature · 1 line
2.52.0