From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Lukas Wunner" <lukas@wunner.de>,
"David Howells" <dhowells@redhat.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Cc: <keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: [PATCH v2] X.509: Introduce scope-based x509_certificate allocation
Date: Mon, 12 Feb 2024 20:10:12 +0200 [thread overview]
Message-ID: <CZ3AWA73R7UO.3OAQ0O5SMIFIE@kernel.org> (raw)
In-Reply-To: <4143b15418c4ecf87ddeceb36813943c3ede17aa.1707734526.git.lukas@wunner.de>
On Mon Feb 12, 2024 at 1:24 PM EET, Lukas Wunner wrote:
> Jonathan suggests adding cleanup.h support for x509_certificate structs.
Please remove as this is just repeating suggested-by tag.
> cleanup.h is a newly introduced way to automatically free allocations at
> end of scope: https://lwn.net/Articles/934679/
cleanup.h is not a feature, it is a header file.
Use link tag for LWN and I guess the feature is called scoped based
resource maangement.
BR, Jarkko
next prev parent reply other threads:[~2024-02-12 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 11:24 [PATCH v2] X.509: Introduce scope-based x509_certificate allocation Lukas Wunner
2024-02-12 12:19 ` Andy Shevchenko
2024-02-12 16:36 ` Lukas Wunner
2024-02-12 18:10 ` Jarkko Sakkinen [this message]
2024-02-12 19:07 ` Dan Williams
2024-02-12 19:20 ` Lukas Wunner
2024-02-12 20:57 ` Dan Williams
2024-02-13 5:04 ` Lukas Wunner
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=CZ3AWA73R7UO.3OAQ0O5SMIFIE@kernel.org \
--to=jarkko@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.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.