From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, tglx@linutronix.de,
kurt@linutronix.de
Subject: Re: [PATCH v5 net-next 0/8]
Date: Fri, 02 Dec 2022 04:40:17 +0000 [thread overview]
Message-ID: <166995601725.2394.13228944085745632127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221129164815.128922-1-bigeasy@linutronix.de>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Nov 2022 17:48:07 +0100 you wrote:
> I started playing with HSR and run into a problem. Tested latest
> upstream -rc and noticed more problems. Now it appears to work.
> For testing I have a small three node setup with iperf and ping. While
> iperf doesn't complain ping reports missing packets and duplicates.
>
> v4…v5:
> - Added __rcu annotation ub patch #7
> - Spelling fixes in #2 and #6.
>
> [...]
Here is the summary with links:
- [v5,net-next,1/8] Revert "net: hsr: use hlist_head instead of list_head for mac addresses"
(no matching commit)
- [v5,net-next,2/8] hsr: Add a rcu-read lock to hsr_forward_skb().
https://git.kernel.org/netdev/net-next/c/5aa2820177af
- [v5,net-next,3/8] hsr: Avoid double remove of a node.
https://git.kernel.org/netdev/net-next/c/0c74d9f79ec4
- [v5,net-next,4/8] hsr: Disable netpoll.
https://git.kernel.org/netdev/net-next/c/d5c7652eb16f
- [v5,net-next,5/8] hsr: Synchronize sending frames to have always incremented outgoing seq nr.
https://git.kernel.org/netdev/net-next/c/06afd2c31d33
- [v5,net-next,6/8] hsr: Synchronize sequence number updates.
https://git.kernel.org/netdev/net-next/c/5c7aa13210c3
- [v5,net-next,7/8] hsr: Use a single struct for self_node.
https://git.kernel.org/netdev/net-next/c/20d3c1e9b861
- [v5,net-next,8/8] selftests: Add a basic HSR test.
https://git.kernel.org/netdev/net-next/c/7d0455e97072
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-12-02 4:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 16:48 [PATCH v5 net-next 0/8] Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 1/8] Revert "net: hsr: use hlist_head instead of list_head for mac addresses" Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 2/8] hsr: Add a rcu-read lock to hsr_forward_skb() Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 3/8] hsr: Avoid double remove of a node Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 4/8] hsr: Disable netpoll Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 5/8] hsr: Synchronize sending frames to have always incremented outgoing seq nr Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 6/8] hsr: Synchronize sequence number updates Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 7/8] hsr: Use a single struct for self_node Sebastian Andrzej Siewior
2022-11-29 16:48 ` [PATCH v5 net-next 8/8] selftests: Add a basic HSR test Sebastian Andrzej Siewior
2022-12-02 4:40 ` 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=166995601725.2394.13228944085745632127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tglx@linutronix.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 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.