From: Markus Elfring <Markus.Elfring@web.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, kernel-janitors@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [v2] crypto: lib/mpi - Extend support for scope-based resource management
Date: Thu, 10 Oct 2024 11:10:30 +0200 [thread overview]
Message-ID: <1df1df73-e741-4ebe-9514-8466b4b276e8@web.de> (raw)
In-Reply-To: <ZweXlC7G8rEK9rB7@gondor.apana.org.au>
>> Do you find the proposed software extension generally reasonable?
>>
>> Can any more source code places benefit from such a programming interface adjustment?
>> https://elixir.bootlin.com/linux/v6.12-rc2/A/ident/mpi_free
>
> Please submit actual patches using this.
I would appreciate more positive indications according to scope-based resource management
extensions before.
I hope that change resistance/acceptance can be clarified already.
Would there be a need to make the activation of discussed special macro calls
depend on other constraints?
Regards,
Markus
next prev parent reply other threads:[~2024-10-10 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 9:33 [PATCH] " 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 [this message]
2024-10-12 15:00 ` [PATCH v3 0/3] lib: Extending " Markus Elfring
2024-10-12 15:05 ` [PATCH v3 1/3] crypto: lib/mpi - Extend " 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=1df1df73-e741-4ebe-9514-8466b4b276e8@web.de \
--to=markus.elfring@web.de \
--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=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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®