From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 850A9C433F5 for ; Mon, 10 Oct 2022 17:39:29 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 95D936B0071; Mon, 10 Oct 2022 13:39:28 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 8E65B6B0073; Mon, 10 Oct 2022 13:39:28 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 75FC96B0074; Mon, 10 Oct 2022 13:39:28 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 65C1A6B0071 for ; Mon, 10 Oct 2022 13:39:28 -0400 (EDT) Received: from smtpin22.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 2E52E16040D for ; Mon, 10 Oct 2022 17:39:28 +0000 (UTC) X-FDA: 80005751616.22.24417FC Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) by imf28.hostedemail.com (Postfix) with ESMTP id C850EC002A for ; Mon, 10 Oct 2022 17:39:26 +0000 (UTC) Received: by mail-oi1-f173.google.com with SMTP id x188so4446542oig.5 for ; Mon, 10 Oct 2022 10:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fXqpXa4IyHrDSP2AtB2YWiprFebXlxfr4+UnrmeiBVA=; b=KqviEEBaSdVH2q+WuAtppLJiJW/8K6S5Glb5rAQ1xGk2IYY4NmIr7n1xHK2pgCGJ65 znOSOrK76CINQtx3yf5p2bq5o0lAFX5Fzj3ydTXddzJFvd+3aFgudyg4m7sUtD/0Egr+ Iy0W1VBbhV+D5CKtpTeWh7wiBEkb52P/V1czk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fXqpXa4IyHrDSP2AtB2YWiprFebXlxfr4+UnrmeiBVA=; b=OjkTiTeboFYrP+dh1PjbP3MhFFF2kZP0iDGnaLtvzcorAzPJWbJ5xKltfT++BKg2rx 5LSl3q/9Er5MrQQKlfGEdw8wAhEUv1geBW91HF3B/4cPeUQ3okcNeOGPoJE+SkzhqA16 QtqUV/MrqQIr5TrUNzHLP8WO+cWPr21Z4h9w8CFfiab4Xc5usKvJv/pmSW1DH56yqUBd TgtddV4n4rCSTeRkQ+7gzXzKyOIjWfEjbrQxp/2x2q93Zf8TzWHzNIbkIqT+Lh95rovE /Sm7oHIEWU4G0qQaf50O2dNwkGxuKnoKnh14UC0C4JW/ZGE75sGntNmXvQQDR8oiAg9F ta4w== X-Gm-Message-State: ACrzQf1thVJX6s4+4LV84UukBwLqtj7QUhFhaRu9owMqQlwSZEgPAw2f wbAFKqauDR/406xOb0LOTiOrNxnvpLOnEw== X-Google-Smtp-Source: AMsMyM7K08wWoqj05/1ZzeBacXBXheg6AotIzEaDhTLC4WRychxkZij9m6h/LQkP1KXO3pcYlJPLIA== X-Received: by 2002:aca:c2c1:0:b0:353:9680:6e3c with SMTP id s184-20020acac2c1000000b0035396806e3cmr14812712oif.105.1665423565436; Mon, 10 Oct 2022 10:39:25 -0700 (PDT) Received: from mail-oa1-f48.google.com (mail-oa1-f48.google.com. [209.85.160.48]) by smtp.gmail.com with ESMTPSA id m26-20020a4ae3da000000b00476995b5f0fsm4385916oov.9.2022.10.10.10.39.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Oct 2022 10:39:23 -0700 (PDT) Received: by mail-oa1-f48.google.com with SMTP id 586e51a60fabf-1326637be6eso13197652fac.13 for ; Mon, 10 Oct 2022 10:39:23 -0700 (PDT) X-Received: by 2002:a05:6870:c0c9:b0:127:c4df:5b50 with SMTP id e9-20020a056870c0c900b00127c4df5b50mr10186924oad.126.1665423562950; Mon, 10 Oct 2022 10:39:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Linus Torvalds Date: Mon, 10 Oct 2022 10:39:06 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [GIT PULL] slab changes for 6.1-rc1 To: Vlastimil Babka Cc: David Rientjes , Joonsoo Kim , Christoph Lameter , Pekka Enberg , Andrew Morton , "linux-mm@kvack.org" , LKML , patches@lists.linux.dev, Roman Gushchin , Hyeonggon Yoo <42.hyeyoo@gmail.com>, Kees Cook , Feng Tang Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1665423566; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=fXqpXa4IyHrDSP2AtB2YWiprFebXlxfr4+UnrmeiBVA=; b=v4hxaSklpnzuAsbbyp+eaLum3IFpqVqp7tj+GRM+y3iGtKMTqnwOtXViX9zXjHkuiX4KMF SoECScLfN7wrQ6UD4FQavxlJuUVKlm88t5mMhoN6UDu3biFGIiAD2b9HGDfVmHHzaqSKGM zgOVSqg+9lP3dDspGjBuOHt6NwiKqE4= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=google header.b=KqviEEBa; spf=pass (imf28.hostedemail.com: domain of torvalds@linuxfoundation.org designates 209.85.167.173 as permitted sender) smtp.mailfrom=torvalds@linuxfoundation.org; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1665423566; a=rsa-sha256; cv=none; b=GLoFM4KziuyzmDsKyjDsXnqpdlVh6EWmlxdYQabd1lD1O3c4YEhFuoTRTDP/tFhbKm9ddt 7N0SgT+hrT/ZN5XC0P2F+uX/IL8YyaQsgC/O28griDLwWhcfXOUypvacVE793X1rjWEoM4 af0CxU85Yv8ZOmWYRj693QMJmJP1Oww= Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=google header.b=KqviEEBa; spf=pass (imf28.hostedemail.com: domain of torvalds@linuxfoundation.org designates 209.85.167.173 as permitted sender) smtp.mailfrom=torvalds@linuxfoundation.org; dmarc=none X-Rspam-User: X-Rspamd-Server: rspam04 X-Stat-Signature: scom6tmruczbsqdxnataaey53krwajcq X-Rspamd-Queue-Id: C850EC002A X-HE-Tag: 1665423566-319933 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Oct 3, 2022 at 9:07 AM Vlastimil Babka wrote: > > This time I tried using topic branches much more than previously, hopefully in > an acceptable way. After rc5-ish I also tried to stabilize their merging into > for-next (and thus the resulting for-6.1) as well. Hence branches > slab/for-6.1/trivial and slab/for-6.1/slub_validation_locking appear to be > merged twice due an extra cleanup and fix, respectivelly, being added and > merged only last week. In slab/for-6.1/kmalloc_size_roundup I however decided > for squashing a fix last week [1] to avoid needless build errors while bisecting. Looks good to me. And thanks to the topic branches, you can actually see the different series (particularly that "common kmalloc" one clearly in the history. Thanks, Linus