netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Beniamino Galvani <b.galvani@gmail.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next] ip: do not print stray prefixes in monitor mode
Date: Thu, 18 Jul 2024 00:00:32 +0000	[thread overview]
Message-ID: <172126083257.7578.12587091201967563672.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240713145641.4145324-1-b.galvani@gmail.com>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Sat, 13 Jul 2024 16:56:41 +0200 you wrote:
> When running "ip monitor", accept_msg() first prints the prefix and
> then calls the object-specific print function, which also does the
> filtering. Therefore, it is possible that the prefix is printed even
> for events that get ignored later. For example:
> 
>   ip link add dummy1 type dummy
>   ip link set dummy1 up
>   ip -ts monitor all dev dummy1 &
>   ip link add dummy2 type dummy
>   ip addr add dev dummy1 192.0.2.1/24
> 
> [...]

Here is the summary with links:
  - [iproute2-next] ip: do not print stray prefixes in monitor mode
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=554ea3649dd1

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



      reply	other threads:[~2024-07-18  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 14:56 [PATCH iproute2-next] ip: do not print stray prefixes in monitor mode Beniamino Galvani
2024-07-18  0:00 ` 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=172126083257.7578.12587091201967563672.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=b.galvani@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).