From: Linus Torvalds <torvalds@linux-foundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Kees Cook <keescook@chromium.org>,
Feng Tang <feng.tang@intel.com>
Subject: Re: [GIT PULL] slab changes for 6.1-rc1
Date: Mon, 10 Oct 2022 10:39:06 -0700 [thread overview]
Message-ID: <CAHk-=wiUA_3pO2jSsMZauVibx20fSdZV+aan217fy+MuGDJT8A@mail.gmail.com> (raw)
In-Reply-To: <d1eaa4f7-6b88-9c14-91d2-84cdbd4b8a31@suse.cz>
On Mon, Oct 3, 2022 at 9:07 AM Vlastimil Babka <vbabka@suse.cz> 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
next prev parent reply other threads:[~2022-10-10 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:06 Vlastimil Babka
2022-10-10 17:39 ` Linus Torvalds [this message]
2022-10-10 18:47 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHk-=wiUA_3pO2jSsMZauVibx20fSdZV+aan217fy+MuGDJT8A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox