[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zzll9v3dR8UxwvQ8@sashalap>
Date: Sat, 16 Nov 2024 22:41:42 -0500
From: Sasha Levin <sashal@...nel.org>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: brauner@...nel.org, viro@...iv.linux.org.uk,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Christoph Lameter <cl@...ux.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Hyeonggon Yoo <42.hyeyoo@...il.com>
Subject: Re: [GIT PULL] slab updates for 6.13
On Sat, Nov 16, 2024 at 09:43:07PM +0100, Vlastimil Babka wrote:
>On 11/16/24 16:35, Sasha Levin wrote:
>> [ Obviously I fat-fingered it and didn't add Christian or Al ]
>
>I have found the problem and looks like I managed to force push an older
>broken version of a branch, possibly due to switching between two computers.
>Serves me well for amending in some last minute R-b tags. Doing git diff
>@{u} to check for unexpected suprirses before pushing the result didn't help
>this time, either I forgot or was blind.
>
>I have deleted the slab-for-6.13 signed tag and pushed the fixed branch only
>to -next. Thanks a lot Sasha for catching this early and please drop the
>merge from the for-linus tree.
I've dropped the merge and tests are passing now, thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists