[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af1a189f-4eeb-8bc2-fe60-ff317a3963f6@amd.com>
Date: Mon, 28 Mar 2022 09:09:04 -0500
From: Carlos Bilbao <carlos.bilbao@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, yazen.ghannam@....com,
linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
bilbao@...edu
Subject: Re: [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and
include messages for panic cases
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
Powered by blists - more mailing lists