linux-kernel - Re: [PATCH v3 2/2] x86/xstate: Make AVX512 status tracking more accurate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFUsyfKQFQqP8ooY8UyJ3TXaZr9TxVOYV78a02-n5c-i22B5Jw@mail.gmail.com>
Date:   Wed, 3 Nov 2021 15:56:34 -0500
From:   Noah Goldstein <goldstein.w.n@...il.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     tglx@...utronix.de, mingo@...hat.com, X86 ML <x86@...nel.org>,
        hpa@...or.com, Andy Lutomirski <luto@...nel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] x86/xstate: Make AVX512 status tracking more accurate

On Wed, Nov 3, 2021 at 3:48 PM Borislav Petkov <bp@...en8.de> wrote:
>
> On Wed, Nov 03, 2021 at 03:22:38PM -0500, Noah Goldstein wrote:
> > Ping.
>
> Dear Noah,
>
> in case you don't know, we have a merge window now. See below for a
> lenghty explanation what that means about new patches.
>
> Also, there's no need to constantly ping people - your patch has landed
> on my TODO list and will be dealt with when its time comes.


Sorry. Don't mean to pressure. Just didn't know the state it had landed.

Thank you for taking care of it :)

>
> If it is a serious bug fix, it will be handled with a higher priority
> but that is not the case, as far as I see it.
>
> So please sit back and be patient - it'll happen.
>
> Thx.
>
> "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."
>
> from Documentation/process/maintainer-tip.rst
>
> --
> Regards/Gruss,
>     Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette