From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>, Linux Networking <netdev@vger.kernel.org>
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, corbet@lwn.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [patch net-next v3] docs: netlink: add NLMSG_DONE message format for doit actions
Date: Sat, 2 Dec 2023 11:49:15 +0700 [thread overview]
Message-ID: <ZWq3S_EEFfCaaEGf@archie.me> (raw)
In-Reply-To: <20231201180154.864007-1-jiri@resnulli.us>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Fri, Dec 01, 2023 at 07:01:54PM +0100, Jiri Pirko wrote:
> diff --git a/Documentation/userspace-api/netlink/intro.rst b/Documentation/userspace-api/netlink/intro.rst
> index 7b1d401210ef..aacffade8f84 100644
> --- a/Documentation/userspace-api/netlink/intro.rst
> +++ b/Documentation/userspace-api/netlink/intro.rst
> @@ -234,6 +234,10 @@ ACK attributes may be present::
> | ** optionally extended ACK |
> ----------------------------------------------
>
> +Note that some implementations may issue custom ``NLMSG_DONE`` messages
> +in reply to ``do`` action requests. In that case the payload is
> +implementation-specific and may also be absent.
> +
> .. _res_fam:
>
> Resolving the Family ID
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-02 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 18:01 [patch net-next v3] docs: netlink: add NLMSG_DONE message format for doit actions Jiri Pirko
2023-12-02 2:28 ` Jakub Kicinski
2023-12-02 4:49 ` Bagas Sanjaya [this message]
2023-12-04 22:50 ` patchwork-bot+netdevbpf
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=ZWq3S_EEFfCaaEGf@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.