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

[RFC v3 0/4] Kernel API Specification Framework with kerneldoc integration · Sasha Levin <sashal@kernel.org> · 2025-07-11
[RFC v3 1/4] kernel/api: introduce kernel API specification framework · Sasha Levin <sashal@kernel.org> · 2025-07-11
Re: [RFC v3 1/4] kernel/api: introduce kernel API specification framework · Askar Safin <hidden> · 2025-07-16
Re: [RFC v3 1/4] kernel/api: introduce kernel API specification framework · Sasha Levin <sashal@kernel.org> · 2025-08-01
[RFC v3 3/4] mm/mlock: add API specification for mlock · Sasha Levin <sashal@kernel.org> · 2025-07-11
[RFC v3 2/4] kernel/api: enable kerneldoc-based API specifications · Sasha Levin <sashal@kernel.org> · 2025-07-11
Re: [RFC v3 2/4] kernel/api: enable kerneldoc-based API specifications · Randy Dunlap <hidden> · 2025-07-21
Re: [RFC v3 2/4] kernel/api: enable kerneldoc-based API specifications · Sasha Levin <sashal@kernel.org> · 2025-07-21
Re: [RFC v3 2/4] kernel/api: enable kerneldoc-based API specifications · Randy Dunlap <hidden> · 2025-07-21
[RFC v3 4/4] kernel/sched: add specs for sys_sched_setattr() · Sasha Levin <sashal@kernel.org> · 2025-07-11

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

From: Askar Safin <hidden>
Date: 2025-07-16 07:21:55
Also in: linux-doc, lkml, tools

+   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

--
Askar Safin