[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51baad8c-6997-4e3b-81df-6d0380fc48d0@web.de>
Date: Fri, 17 Oct 2025 13:06:27 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Pavitrakumar Managutte <pavitrakumarm@...avyalabs.com>,
linux-crypto@...r.kernel.org, devicetree@...r.kernel.org
Cc: Bhoomika Kadabi <bhoomikak@...avyalabs.com>,
Manjunath Hadli <manjunath.hadli@...avyalabs.com>,
Ruud Derwig <Ruud.Derwig@...opsys.com>,
Herbert Xu <herbert@...dor.apana.org.au>, Rob Herring <robh@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Aditya Kulkarni <adityak@...avyalabs.com>, Conor Dooley
<conor+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
T Pratham <t-pratham@...com>
Subject: Re: [PATCH v7 2/4] Add SPAcc ahash support
>> …
>>> +do_shash_err:
>>> + crypto_free_shash(hash);
>>> + kfree(sdesc);
>>> +
>>> + return rc;
>>> +}
>> …
>>
>> * You may use an additional label for better exception handling.
> PK: Ack, I will go with an additional label.
Can scope-based resource management become applicable for more use cases?
Regards,
Markus
Powered by blists - more mailing lists