Re: [PATCH] crypto: replace broken libkcapi link in Crypto API documentation

[Paul Louvel <paul.louvel@bootlin.com>]

Hi,

I have just checked this morning on the same browser, and indeed, it works.
It was broken for the past few days.
Please ignore this patch then.

Regards,
Paul.

On 3/14/26 12:46 AM, Randy Dunlap wrote:
>
> On 3/13/26 3:00 PM, Paul Louvel via B4 Relay wrote:
>> From: Paul Louvel <paul.louvel@bootlin.com>
>>
>> The "User Space Interface" section of the Crypto API documentation
>> contains a link to the libkcapi project that no longer works.
>>
>> Update the link to point to the correct upstream location so that
>> users can access the library documentation.
>>
>> Signed-off-by: Paul Louvel <paul.louvel@bootlin.com>
>> ---
>> The "User Space Interface" of the Crypto API documentation has a broken
>> link to libkcapi. Replacing it with a working one.
>> ---
>>   Documentation/crypto/userspace-if.rst | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/crypto/userspace-if.rst b/Documentation/crypto/userspace-if.rst
>> index 021759198fe7..79e41845f611 100644
>> --- a/Documentation/crypto/userspace-if.rst
>> +++ b/Documentation/crypto/userspace-if.rst
>> @@ -23,7 +23,7 @@ user space, however. This includes the difference between synchronous
>>   and asynchronous invocations. The user space API call is fully
>>   synchronous.
>>   
>> -[1] https://www.chronox.de/libkcapi/index.html
>> +[1] https://www.chronox.de/libkcapi/
>>   
>>   User Space API General Remarks
>>   ------------------------------
>> @@ -406,4 +406,4 @@ Please see [1] for libkcapi which provides an easy-to-use wrapper around
>>   the aforementioned Netlink kernel interface. [1] also contains a test
>>   application that invokes all libkcapi API calls.
>>   
>> -[1] https://www.chronox.de/libkcapi/index.html
>> +[1] https://www.chronox.de/libkcapi/
>>
>> ---
>> base-commit: b84a0ebe421ca56995ff78b66307667b62b3a900
>> change-id: 20260313-crypto-api-libkcapi-broken-link-65069e8ce688
>>
>> Best regards,
> Hi,
> Either link works for me (with the same content).
> Could it be browser-dependent?
>
>
-- 
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com