From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, johannes@sipsolutions.net,
pablo@netfilter.org, fw@strlen.de, jhs@mojatatu.com,
jacob.e.keller@intel.com, florent.fourcot@wifirst.fr,
gnault@redhat.com, nicolas.dichtel@6wind.com,
razor@blackwall.org, liuhangbin@gmail.com
Subject: Re: [PATCH net-next] docs: netlink: clarify the historical baggage of Netlink flags
Date: Fri, 30 Sep 2022 02:21:06 +0000 [thread overview]
Message-ID: <166450446641.30186.4808131055717975965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220927212306.823862-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Sep 2022 14:23:06 -0700 you wrote:
> nlmsg_flags are full of historical baggage, inconsistencies and
> strangeness. Try to document it more thoroughly. Explain the meaning
> of the ECHO flag (and while at it clarify the comment in the uAPI).
> Handwave a little about the NEW request flags and how they make
> sense on the surface but cater to really old paradigm before commands
> were a thing.
>
> [...]
Here is the summary with links:
- [net-next] docs: netlink: clarify the historical baggage of Netlink flags
https://git.kernel.org/netdev/net-next/c/5493a2ad0d20
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-30 2:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 21:23 [PATCH net-next] docs: netlink: clarify the historical baggage of Netlink flags Jakub Kicinski
2022-09-28 7:03 ` Nikolay Aleksandrov
2022-09-28 14:21 ` Jakub Kicinski
2022-09-28 14:40 ` Nikolay Aleksandrov
2022-09-28 14:43 ` Nikolay Aleksandrov
2022-09-30 11:07 ` Jamal Hadi Salim
2022-09-30 11:29 ` Nikolay Aleksandrov
2022-09-30 14:24 ` Jamal Hadi Salim
2022-09-30 14:34 ` Nikolay Aleksandrov
2022-09-30 16:36 ` Jamal Hadi Salim
2022-09-30 18:19 ` Nikolay Aleksandrov
2022-10-02 13:59 ` Jamal Hadi Salim
2022-09-28 8:04 ` Florent Fourcot
2022-09-28 8:55 ` Nicolas Dichtel
2022-09-28 9:21 ` Nikolay Aleksandrov
2022-09-28 14:37 ` Jakub Kicinski
2022-09-28 14:46 ` Nikolay Aleksandrov
2022-09-28 15:15 ` Jakub Kicinski
2022-09-28 15:19 ` Nicolas Dichtel
2022-09-30 2:21 ` patchwork-bot+netdevbpf [this message]
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=166450446641.30186.4808131055717975965.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florent.fourcot@wifirst.fr \
--cc=fw@strlen.de \
--cc=gnault@redhat.com \
--cc=jacob.e.keller@intel.com \
--cc=jhs@mojatatu.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.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.