From: patchwork-bot+netdevbpf@kernel.org
To: Matteo Croce <mcroce@linux.microsoft.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, yoshfuji@linux-ipv6.org, kuba@kernel.org
Subject: Re: [PATCH net 0/2] ipv6: fixes for the multicast routes
Date: Tue, 19 Jan 2021 04:00:08 +0000 [thread overview]
Message-ID: <161102880877.24762.7105009788756297504.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210115184209.78611-1-mcroce@linux.microsoft.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Fri, 15 Jan 2021 19:42:07 +0100 you wrote:
> From: Matteo Croce <mcroce@microsoft.com>
>
> Fix two wrong flags in the IPv6 multicast routes created
> by the autoconf code.
>
> Matteo Croce (2):
> ipv6: create multicast route with RTPROT_KERNEL
> ipv6: set multicast flag on the multicast route
>
> [...]
Here is the summary with links:
- [net,1/2] ipv6: create multicast route with RTPROT_KERNEL
https://git.kernel.org/netdev/net/c/a826b04303a4
- [net,2/2] ipv6: set multicast flag on the multicast route
https://git.kernel.org/netdev/net/c/ceed9038b278
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:[~2021-01-19 4:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 18:42 [PATCH net 0/2] ipv6: fixes for the multicast routes Matteo Croce
2021-01-15 18:42 ` [PATCH net 1/2] ipv6: create multicast route with RTPROT_KERNEL Matteo Croce
2021-01-16 4:36 ` David Ahern
2021-01-16 12:17 ` Matteo Croce
2021-01-15 18:42 ` [PATCH net 2/2] ipv6: set multicast flag on the multicast route Matteo Croce
2021-01-15 22:50 ` [PATCH net 0/2] ipv6: fixes for the multicast routes Jakub Kicinski
2021-01-15 23:12 ` Matteo Croce
2021-01-16 4:41 ` David Ahern
2021-01-17 2:28 ` Matteo Croce
2021-01-19 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=161102880877.24762.7105009788756297504.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@linux.microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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.