From: Markus Elfring <Markus.Elfring@web.de>
To: linux-crypto@vger.kernel.org, kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/3] lib: Extending support for scope-based resource management
Date: Sat, 12 Oct 2024 17:00:26 +0200 [thread overview]
Message-ID: <ee5f409e-4412-41cd-b8d8-92872770f04d@web.de> (raw)
In-Reply-To: <ZweTCO8cFtP_pvOu@gondor.apana.org.au>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 12 Oct 2024 15:48:05 +0200
Some development ideas were taken into account according to evolving discussions.
Markus Elfring (3):
crypto: lib/mpi - Extend support for scope-based resource management
lib/digsig: Use scope-based resource management for two MPI variables
in digsig_verify_rsa()
lib/digsig: Use scope-based resource management for two variables
in digsig_verify_rsa()
include/linux/mpi.h | 4 ++
lib/digsig.c | 107 +++++++++++++++++++++++---------------------
2 files changed, 59 insertions(+), 52 deletions(-)
V3:
* Applications were added as requested (by Herbert Xu) for the proposed
programming interface extension.
* Further adjustments were provided for the demonstration of an evolving
programming interface.
V2:
The kernel build service pointed out that the proposed identifier “T_”
was not recognised by the compiler.
Thus reserved identifiers need still be applied also at such a place instead
so far.
I became curious under which circumstances corresponding development concerns
will be reconsidered any more.
--
2.46.1
next prev parent reply other threads:[~2024-10-12 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 9:33 [PATCH] crypto: lib/mpi - Extend " Markus Elfring
2024-09-17 23:27 ` kernel test robot
2024-09-18 9:26 ` [PATCH v2] " Markus Elfring
2024-10-05 5:33 ` Herbert Xu
2024-10-05 6:27 ` [PATCH v2 RESEND] " Markus Elfring
2024-10-10 8:40 ` Herbert Xu
2024-10-10 8:58 ` [v2] " Markus Elfring
2024-10-10 9:00 ` Herbert Xu
2024-10-10 9:10 ` Markus Elfring
2024-10-12 15:00 ` Markus Elfring [this message]
2024-10-12 15:05 ` [PATCH v3 1/3] " Markus Elfring
2024-10-12 15:08 ` [PATCH v3 2/3] lib/digsig: Use scope-based resource management for two MPI variables in digsig_verify_rsa() Markus Elfring
2024-10-15 21:27 ` kernel test robot
2024-10-16 11:21 ` kernel test robot
2024-10-12 15:10 ` [PATCH v3 3/3] lib/digsig: Use scope-based resource management for two " Markus Elfring
2024-09-18 0:52 ` [PATCH] crypto: lib/mpi - Extend support for scope-based resource management kernel test robot
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=ee5f409e-4412-41cd-b8d8-92872770f04d@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®