From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, linus.luessing@c0d3.blue,
sven@narfation.org
Subject: Re: [PATCH 1/1] batman-adv: mcast: don't send link-local multicast to mcast routers
Date: Tue, 04 Jan 2022 04:00:11 +0000 [thread overview]
Message-ID: <164126881175.32247.1012598310655037825.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220103171203.1124980-2-sw@simonwunderlich.de>
Hello:
This patch was applied to netdev/net.git (master)
by Simon Wunderlich <sw@simonwunderlich.de>:
On Mon, 3 Jan 2022 18:12:03 +0100 you wrote:
> From: Linus Lüssing <linus.luessing@c0d3.blue>
>
> The addition of routable multicast TX handling introduced a
> bug/regression for packets with a link-local multicast destination:
> These packets would be sent to all batman-adv nodes with a multicast
> router and to all batman-adv nodes with an old version without multicast
> router detection.
>
> [...]
Here is the summary with links:
- [1/1] batman-adv: mcast: don't send link-local multicast to mcast routers
https://git.kernel.org/netdev/net/c/938f2e0b57ff
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-01-04 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 17:12 [PATCH 0/1] pull request for net: batman-adv 2022-01-03 Simon Wunderlich
2022-01-03 17:12 ` [PATCH 1/1] batman-adv: mcast: don't send link-local multicast to mcast routers Simon Wunderlich
2022-01-04 4: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=164126881175.32247.1012598310655037825.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).