| Message ID | 20220328134131.736572-1-carlos.bilbao@amd.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases | expand |
On Mon, Mar 28, 2022 at 08:41:30AM -0500, Carlos Bilbao wrote: > This patchset includes grading of new types of machine errors on AMD's MCE > grading logic mce_severity_amd(), which helps the MCE handler determine > what actions to take. If the error is graded as a PANIC, the EDAC driver > will not decode; so we also include new error messages to describe the MCE > and help debugging critical errors. > > Carlos Bilbao (2): > x86/mce: Extend AMD severity grading function with new types of errors > x86/mce: Add messages to describe panic machine errors on AMD's MCEs grading > > arch/x86/include/asm/mce.h | 6 + > arch/x86/kernel/cpu/mce/severity.c | 203 ++++++++++++++++++++++++----- > 2 files changed, 174 insertions(+), 35 deletions(-) How is this submission different from https://lore.kernel.org/r/20220311165114.482074-1-carlos.bilbao@amd.com ?
On 3/28/2022 8:55 AM, Borislav Petkov wrote: > On Mon, Mar 28, 2022 at 08:41:30AM -0500, Carlos Bilbao wrote: >> This patchset includes grading of new types of machine errors on AMD's MCE >> grading logic mce_severity_amd(), which helps the MCE handler determine >> what actions to take. If the error is graded as a PANIC, the EDAC driver >> will not decode; so we also include new error messages to describe the MCE >> and help debugging critical errors. >> >> Carlos Bilbao (2): >> x86/mce: Extend AMD severity grading function with new types of errors >> x86/mce: Add messages to describe panic machine errors on AMD's MCEs grading >> >> arch/x86/include/asm/mce.h | 6 + >> arch/x86/kernel/cpu/mce/severity.c | 203 ++++++++++++++++++++++++----- >> 2 files changed, 174 insertions(+), 35 deletions(-) > > How is this submission different from > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fr%2F20220311165114.482074-1-carlos.bilbao%40amd.com&data=04%7C01%7Ccarlos.bilbao%40amd.com%7C7355a7de9b224557d6cf08da10c29e56%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637840725342715892%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=A809HxzZHYiZQ6Arlje0o9KAFt4c77I2Q4vOfCl9%2Fis%3D&reserved=0 > > ? Just fixed a typo in the first patch -I should have included a change log. Thanks, Carlos >
On Mon, Mar 28, 2022 at 08:57:04AM -0500, Carlos Bilbao wrote:
> Just fixed a typo in the first patch -I should have included a change log.
Well, we have the merge window open currently:
Merge window
^^^^^^^^^^^^
Please do not expect large patch series to be handled during the merge
window or even during the week before. Such patches should be submitted in
mergeable state *at* *least* a week before the merge window opens.
Exceptions are made for bug fixes and *sometimes* for small standalone
drivers for new hardware or minimally invasive patches for hardware
enablement.
During the merge window, the maintainers instead focus on following the
upstream changes, fixing merge window fallout, collecting bug fixes, and
allowing themselves a breath. Please respect that.
The release candidate -rc1 is the starting point for new patches to be
applied which are targeted for the next merge window.
---
and since you're new to this, I'd suggest you take the
time to read Documentation/process/ and especially
Documentation/process/submitting-patches.rst while waiting.
Thx.
On 3/28/2022 9:04 AM, Borislav Petkov wrote: > On Mon, Mar 28, 2022 at 08:57:04AM -0500, Carlos Bilbao wrote: >> Just fixed a typo in the first patch -I should have included a change log. > > Well, we have the merge window open currently: > > Merge window > ^^^^^^^^^^^^ > > Please do not expect large patch series to be handled during the merge > window or even during the week before. Such patches should be submitted in > mergeable state *at* *least* a week before the merge window opens. > Exceptions are made for bug fixes and *sometimes* for small standalone > drivers for new hardware or minimally invasive patches for hardware > enablement. > > During the merge window, the maintainers instead focus on following the > upstream changes, fixing merge window fallout, collecting bug fixes, and > allowing themselves a breath. Please respect that. > > The release candidate -rc1 is the starting point for new patches to be > applied which are targeted for the next merge window. > > --- > > and since you're new to this, I'd suggest you take the > time to read Documentation/process/ and especially > Documentation/process/submitting-patches.rst while waiting. > > Thx. > Thanks Borislav -would you like me to resend this once -rc1 opens? Best, Carlos
On Mon, Mar 28, 2022 at 09:09:04AM -0500, Carlos Bilbao wrote:
> Thanks Borislav -would you like me to resend this once -rc1 opens?
No need - I have it already. Btw, those documents also explain when
to resend: when the patches need to be changed or when they've been
forgotten. Most people usually send a "ping email" as a reply to the
thread to remind the maintainer to handle them, in that latter case.
Thx.