From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, vinicius.gomes@intel.com,
kurt@linutronix.de, alexandre.belloni@bootlin.com,
xiaoliang.yang_1@nxp.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] Improve tsn_lib selftests for future distributed tasks
Date: Mon, 26 Sep 2022 20:30:16 +0000 [thread overview]
Message-ID: <166422421686.13925.11977641432026324347.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923210016.3406301-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 24 Sep 2022 00:00:11 +0300 you wrote:
> Some of the boards I am working with are limited in the number of ports
> that they offer, and as more TSN related selftests are added, it is
> important to be able to distribute the work among multiple boards.
> A large part of implementing that is ensuring network-wide
> synchronization, but also permitting more streams of data to flow
> through the network. There is the more important aspect of also
> coordinating the timing characteristics of those streams, and that is
> also something that is tackled, although not in this modest patch set.
> The goal here is not to introduce new selftests yet, but just to lay a
> better foundation for them. These patches are a part of the cleanup work
> I've done while working on selftests for frame preemption. They are
> regression-tested with psfp.sh.
>
> [...]
Here is the summary with links:
- [net-next,1/4] selftests: net: tsn_lib: don't overwrite isochron receiver extra args with UDS
https://git.kernel.org/netdev/net-next/c/7d45b5fd27b4
- [net-next,2/4] selftests: net: tsn_lib: allow running ptp4l on multiple interfaces
https://git.kernel.org/netdev/net-next/c/7ff9396ee82c
- [net-next,3/4] selftests: net: tsn_lib: allow multiple isochron receivers
https://git.kernel.org/netdev/net-next/c/a7ce95ac837d
- [net-next,4/4] selftests: net: tsn_lib: run phc2sys in automatic mode
https://git.kernel.org/netdev/net-next/c/162d52dfee44
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-09-26 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 21:00 [PATCH net-next 0/4] Improve tsn_lib selftests for future distributed tasks Vladimir Oltean
2022-09-23 21:00 ` [PATCH net-next 1/4] selftests: net: tsn_lib: don't overwrite isochron receiver extra args with UDS Vladimir Oltean
2022-09-23 21:00 ` [PATCH net-next 2/4] selftests: net: tsn_lib: allow running ptp4l on multiple interfaces Vladimir Oltean
2022-09-23 21:00 ` [PATCH net-next 3/4] selftests: net: tsn_lib: allow multiple isochron receivers Vladimir Oltean
2022-09-23 21:00 ` [PATCH net-next 4/4] selftests: net: tsn_lib: run phc2sys in automatic mode Vladimir Oltean
2022-09-23 21:00 ` Vladimir Oltean
2022-09-24 9:52 ` [PATCH net-next 0/4] Improve tsn_lib selftests for future distributed tasks Kurt Kanzenbach
2022-09-26 20:30 ` 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=166422421686.13925.11977641432026324347.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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 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).