All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Askar Safin <safinaskar@zohomail.com>
Cc: linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, tools@kernel.org
Subject: Re: [RFC v3 1/4] kernel/api: introduce kernel API specification framework
Date: Fri, 1 Aug 2025 09:53:39 -0400	[thread overview]
Message-ID: <aIzG427WYt0_wonN@lappy> (raw)
In-Reply-To: <20250716072141.12-1-safinaskar@zohomail.com>

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

  reply	other threads:[~2025-08-01 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 11:42 [RFC v3 0/4] Kernel API Specification Framework with kerneldoc integration Sasha Levin
2025-07-11 11:42 ` [RFC v3 1/4] kernel/api: introduce kernel API specification framework Sasha Levin
2025-07-12 17:03   ` kernel test robot
2025-07-13  9:39   ` kernel test robot
2025-07-16  7:21   ` Askar Safin
2025-08-01 13:53     ` Sasha Levin [this message]
2025-07-11 11:42 ` [RFC v3 2/4] kernel/api: enable kerneldoc-based API specifications Sasha Levin
2025-07-12  7:16   ` kernel test robot
2025-07-21  0:55   ` Randy Dunlap
2025-07-21  2:54     ` Sasha Levin
2025-07-21  3:17       ` Randy Dunlap
2025-07-11 11:42 ` [RFC v3 3/4] mm/mlock: add API specification for mlock Sasha Levin
2025-07-11 11:42 ` [RFC v3 4/4] kernel/sched: add specs for sys_sched_setattr() Sasha Levin

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=aIzG427WYt0_wonN@lappy \
    --to=sashal@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safinaskar@zohomail.com \
    --cc=tools@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.