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, jiri@resnulli.us, donald.hunter@gmail.com
Subject: Re: [PATCH net-next v2 0/4] tools: ynl: add --dbg-small-recv for easier kernel testing
Date: Wed, 06 Mar 2024 12:10:30 +0000	[thread overview]
Message-ID: <170972703078.11436.219705901018302745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305053310.815877-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon,  4 Mar 2024 21:33:06 -0800 you wrote:
> When testing netlink dumps I usually hack some user space up
> to constrain its user space buffer size (iproute2, ethtool or ynl).
> Netlink will try to fill the messages up, so since these apps use
> large buffers by default, the dumps are rarely fragmented.
> 
> I was hoping to figure out a way to create a selftest for dump
> testing, but so far I have no idea how to do that in a useful
> and generic way.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/4] tools: ynl: move the new line in NlMsg __repr__
    https://git.kernel.org/netdev/net-next/c/7df7231d6a6b
  - [net-next,v2,2/4] tools: ynl: allow setting recv() size
    https://git.kernel.org/netdev/net-next/c/7c93a88785da
  - [net-next,v2,3/4] tools: ynl: support debug printing messages
    https://git.kernel.org/netdev/net-next/c/a6a41521f95e
  - [net-next,v2,4/4] tools: ynl: add --dbg-small-recv for easier kernel testing
    https://git.kernel.org/netdev/net-next/c/c0111878d45e

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-03-06 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  5:33 [PATCH net-next v2 0/4] tools: ynl: add --dbg-small-recv for easier kernel testing Jakub Kicinski
2024-03-05  5:33 ` [PATCH net-next v2 1/4] tools: ynl: move the new line in NlMsg __repr__ Jakub Kicinski
2024-03-05  5:33 ` [PATCH net-next v2 2/4] tools: ynl: allow setting recv() size Jakub Kicinski
2024-03-05 11:04   ` Donald Hunter
2024-03-05  5:33 ` [PATCH net-next v2 3/4] tools: ynl: support debug printing messages Jakub Kicinski
2024-03-05  5:33 ` [PATCH net-next v2 4/4] tools: ynl: add --dbg-small-recv for easier kernel testing Jakub Kicinski
2024-03-05 11:05   ` Donald Hunter
2024-03-06 12:10 ` 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=170972703078.11436.219705901018302745.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=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.