From: Borislav Petkov <bp@alien8.de>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org,
yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases
Date: Mon, 28 Mar 2022 16:04:32 +0200 [thread overview]
Message-ID: <YkHAcIZDpZER9knA@zn.tnic> (raw)
In-Reply-To: <299368f0-a3f3-c252-ab98-7dd324dbd3c5@amd.com>
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.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-03-28 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:41 [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases Carlos Bilbao
2022-03-28 13:41 ` [PATCH 1/2] x86/mce: Extend AMD severity grading function with new types of errors Carlos Bilbao
2022-03-30 20:02 ` Yazen Ghannam
2022-03-31 14:41 ` Carlos Bilbao
2022-03-28 13:41 ` [PATCH 2/2] x86/mce: Add messages to describe panic machine errors on AMD's MCEs grading Carlos Bilbao
2022-03-28 13:55 ` [PATCH 0/2] x86/mce: Grade new machine errors for AMD MCEs and include messages for panic cases Borislav Petkov
2022-03-28 13:57 ` Carlos Bilbao
2022-03-28 14:04 ` Borislav Petkov [this message]
2022-03-28 14:09 ` Carlos Bilbao
2022-03-28 14:16 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2022-03-11 16:51 Carlos Bilbao
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=YkHAcIZDpZER9knA@zn.tnic \
--to=bp@alien8.de \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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