On Wed, Apr 19, 2023 at 01:57:05PM +0000, Alyssa Ross wrote:
On Wed, Apr 19, 2023 at 03:17:13PM +0200, Greg KH wrote:
On Wed, Apr 19, 2023 at 12:26:26PM +0000, Conor.Dooley@microchip.com wrote:
On 19/04/2023 10:40, Greg Kroah-Hartman wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
This is the start of the stable review cycle for the 6.2.12 release. There are 138 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri, 21 Apr 2023 09:36:26 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.2.12-rc2.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.2.y and the diffstat can be found below.
thanks,
greg k-h
Alyssa Ross hi@alyssa.is purgatory: fix disabling debug info
Heiko Stuebner heiko.stuebner@vrull.eu RISC-V: add infrastructure to allow different str* implementations
Lore is ~dead for me right now, but there should be a custom backport of Alyssa's commit, submitted by her, here: https://lore.kernel.org/all/20230417134044.1821014-1-hi@alyssa.is/
Perhaps the reason is just the quantity of email, but that was submitted against the "fail" email (and within a few hours), so why was another commit pulled back instead of using what she provided?
Ok, now both dropped, this got confusing fast.
So what's my next step to getting my patch backported?
Do I have to wait for these kernels to be released, and then submit my backport again and hope it gets selected the second time round?
Yes please, that would be the best, sorry for the trouble, patches were in flight from multiple people and we got confused.
greg k-hj