From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-hardening@vger.kernel.org, Kees Cook <kees@kernel.org>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 6.18 0/4] Backport the one-arg k*alloc_obj() APIs
Date: Fri, 10 Jul 2026 17:03:06 -0400 [thread overview]
Message-ID: <20260710163023.agent5-0010@kernel.org> (raw)
In-Reply-To: <20260709043301.142931-1-ebiggers@kernel.org>
On Thu, Jul 09, 2026 at 12:32:57AM -0400, Eric Biggers wrote:
> After this is applied, dd015b566d50 and 696c030e1e34 will be clean
> cherry-picks, so please cherry-pick those afterwards.
Queued both fscrypt follow-ups for 6.18, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-10 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:32 [PATCH 6.18 0/4] Backport the one-arg k*alloc_obj() APIs Eric Biggers
2026-07-09 4:32 ` [PATCH 6.18 1/4] slab: Introduce kmalloc_flex() and family Eric Biggers
2026-07-09 4:32 ` [PATCH 6.18 2/4] add default_gfp() helper macro and use it in the new *alloc_obj() helpers Eric Biggers
2026-07-09 4:33 ` [PATCH 6.18 3/4] default_gfp(): avoid using the "newfangled" __VA_OPT__ trick Eric Biggers
2026-07-09 4:33 ` [PATCH 6.18 4/4] slab: recognize @GFP parameter as optional in kernel-doc Eric Biggers
2026-07-09 13:07 ` Greg KH
2026-07-10 21:03 ` Sasha Levin [this message]
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=20260710163023.agent5-0010@kernel.org \
--to=sashal@kernel.org \
--cc=ebiggers@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.