linux-kernel - Re: [RFC v3 1/4] kernel/api: introduce kernel API specification framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aIzG427WYt0_wonN@lappy>
Date: Fri, 1 Aug 2025 09:53:39 -0400
From: Sasha Levin <sashal@...nel.org>
To: Askar Safin <safinaskar@...omail.com>
Cc: linux-api@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, tools@...nel.org
Subject: Re: [RFC v3 1/4] kernel/api: introduce kernel API specification
 framework

On Wed, Jul 16, 2025 at 10:21:41AM +0300, Askar Safin wrote:
>> +   KAPI_PARAM_IN       = (1 << 0),
>> +   KAPI_PARAM_OUT      = (1 << 1),
>> +   KAPI_PARAM_INOUT    = (1 << 2),
>
>There is no need for KAPI_PARAM_INOUT. It could be replaced by KAPI_PARAM_IN | KAPI_PARAM_OUT

It could, but it's easier to write _INOUT :)

-- 
Thanks,
Sasha