All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, nicolas.dichtel@6wind.com,
	donald.hunter@gmail.com, jiri@resnulli.us, sdf@google.com
Subject: Re: [PATCH net-next v3 00/15] tools: ynl: stop using libmnl
Date: Wed, 28 Feb 2024 23:50:32 +0000	[thread overview]
Message-ID: <170916423218.30546.12389885775738975150.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227223032.1835527-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 27 Feb 2024 14:30:17 -0800 you wrote:
> There is no strong reason to stop using libmnl in ynl but there
> are a few small ones which add up.
> 
> First (as I remembered immediately after hitting send on v1),
> C++ compilers do not like the libmnl for_each macros.
> I haven't tried it myself, but having all the code directly
> in YNL makes it easier for folks porting to C++ to modify them
> and/or make YNL more C++ friendly.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/15] tools: ynl: give up on libmnl for auto-ints
    https://git.kernel.org/netdev/net-next/c/21f6986d19b0
  - [net-next,v3,02/15] tools: ynl: create local attribute helpers
    https://git.kernel.org/netdev/net-next/c/5600c580383a
  - [net-next,v3,03/15] tools: ynl: create local for_each helpers
    https://git.kernel.org/netdev/net-next/c/66fcdad08842
  - [net-next,v3,04/15] tools: ynl: create local nlmsg access helpers
    https://git.kernel.org/netdev/net-next/c/0b3ece442208
  - [net-next,v3,05/15] tools: ynl: create local ARRAY_SIZE() helper
    https://git.kernel.org/netdev/net-next/c/7600875f295f
  - [net-next,v3,06/15] tools: ynl: make yarg the first member of struct ynl_dump_state
    https://git.kernel.org/netdev/net-next/c/d62c5d487cfe
  - [net-next,v3,07/15] tools: ynl-gen: remove unused parse code
    https://git.kernel.org/netdev/net-next/c/9c29a113165f
  - [net-next,v3,08/15] tools: ynl: wrap recv() + mnl_cb_run2() into a single helper
    https://git.kernel.org/netdev/net-next/c/2f22f0b313f4
  - [net-next,v3,09/15] tools: ynl: use ynl_sock_read_msgs() for ACK handling
    https://git.kernel.org/netdev/net-next/c/1621378aab19
  - [net-next,v3,10/15] tools: ynl: stop using mnl_cb_run2()
    https://git.kernel.org/netdev/net-next/c/766c4b5460f4
  - [net-next,v3,11/15] tools: ynl: switch away from mnl_cb_t
    https://git.kernel.org/netdev/net-next/c/dd0973d71e1f
  - [net-next,v3,12/15] tools: ynl: switch away from MNL_CB_*
    https://git.kernel.org/netdev/net-next/c/50042e8051fe
  - [net-next,v3,13/15] tools: ynl: stop using mnl socket helpers
    https://git.kernel.org/netdev/net-next/c/5ac6868daa0e
  - [net-next,v3,14/15] tools: ynl: remove the libmnl dependency
    https://git.kernel.org/netdev/net-next/c/73395b43819b
  - [net-next,v3,15/15] tools: ynl: use MSG_DONTWAIT for getting notifications
    https://git.kernel.org/netdev/net-next/c/7c4a38bf1eba

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-28 23:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 22:30 [PATCH net-next v3 00/15] tools: ynl: stop using libmnl Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 01/15] tools: ynl: give up on libmnl for auto-ints Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 02/15] tools: ynl: create local attribute helpers Jakub Kicinski
2024-02-28  8:21   ` Nicolas Dichtel
2024-02-27 22:30 ` [PATCH net-next v3 03/15] tools: ynl: create local for_each helpers Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 04/15] tools: ynl: create local nlmsg access helpers Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 05/15] tools: ynl: create local ARRAY_SIZE() helper Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 06/15] tools: ynl: make yarg the first member of struct ynl_dump_state Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 07/15] tools: ynl-gen: remove unused parse code Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 08/15] tools: ynl: wrap recv() + mnl_cb_run2() into a single helper Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 09/15] tools: ynl: use ynl_sock_read_msgs() for ACK handling Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 10/15] tools: ynl: stop using mnl_cb_run2() Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 11/15] tools: ynl: switch away from mnl_cb_t Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 12/15] tools: ynl: switch away from MNL_CB_* Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 13/15] tools: ynl: stop using mnl socket helpers Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 14/15] tools: ynl: remove the libmnl dependency Jakub Kicinski
2024-02-27 22:30 ` [PATCH net-next v3 15/15] tools: ynl: use MSG_DONTWAIT for getting notifications Jakub Kicinski
2024-02-28 23:50 ` 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=170916423218.30546.12389885775738975150.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.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.