From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 6.12] fscrypt: Avoid dynamic allocation in fscrypt_get_devices()
Date: Wed, 29 Jul 2026 22:40:15 -0400 [thread overview]
Message-ID: <20260729223316.stable-0019@kernel.org> (raw)
In-Reply-To: <20260729152127.11918-1-ebiggers@kernel.org>
> [PATCH 6.12] fscrypt: Avoid dynamic allocation in fscrypt_get_devices()
Queued for 6.12, thanks.
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 6.12] fscrypt: Avoid dynamic allocation in fscrypt_get_devices()
Date: Wed, 29 Jul 2026 22:40:15 -0400 [thread overview]
Message-ID: <20260729223316.stable-0019@kernel.org> (raw)
In-Reply-To: <20260729152127.11918-1-ebiggers@kernel.org>
> [PATCH 6.12] fscrypt: Avoid dynamic allocation in fscrypt_get_devices()
Queued for 6.12, thanks.
--
Thanks,
Sasha
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-07-30 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 15:21 [f2fs-dev] [PATCH 6.12] fscrypt: Avoid dynamic allocation in fscrypt_get_devices() Eric Biggers via Linux-f2fs-devel
2026-07-29 15:21 ` Eric Biggers
2026-07-30 2:40 ` Sasha Levin [this message]
2026-07-30 2:40 ` [f2fs-dev] " Sasha Levin via Linux-f2fs-devel
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=20260729223316.stable-0019@kernel.org \
--to=sashal@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@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.