[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250528170920.GEaDdDQEK-pxU13cWu@fat_crate.local>
Date: Wed, 28 May 2025 19:09:20 +0200
From: Borislav Petkov <bp@...en8.de>
To: Ruben Wauters <rubenru09@....com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] x86/cpu/intel: replace deprecated strcpy with
strscpy
Hi,
On Wed, May 28, 2025 at 04:34:51PM +0100, Ruben Wauters wrote:
> I was wondering if there was any chance this patch could be applied? is
> there something I need to do to change it so it's fine? is there
> someone else I need to send it to so they can review it?
>
> I don't want to keep sending and asking about an unwanted patch so if
> this isn't wanted please let me know and I'll move on.
the tip tree is open for new code after the merge window is over.
From: Documentation/process/maintainer-tip.rst
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."
IOW, be patient please. You're not the only one with a patch...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists