From: Ido Schimmel <idosch@idosch.org>
To: kuba@kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
schultz.hans@gmail.com, razor@blackwall.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/2] selftests: forwarding: Locked bridge port fixes
Date: Mon, 21 Mar 2022 19:53:55 +0200 [thread overview]
Message-ID: <Yji7s4qjjEy/SSXx@shredder> (raw)
In-Reply-To: <20220321175102.978020-1-idosch@nvidia.com>
On Mon, Mar 21, 2022 at 07:51:00PM +0200, Ido Schimmel wrote:
> Two fixes for the locked bridge port selftest.
Jakub, I'm aware that net-next is closed, but these are fixes for code
in net-next. If you prefer, I can resubmit later this week after you
merge master to net.
next prev parent reply other threads:[~2022-03-21 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:51 [PATCH net-next 0/2] selftests: forwarding: Locked bridge port fixes Ido Schimmel
2022-03-21 17:51 ` [PATCH net-next 1/2] selftests: forwarding: Disable learning before link up Ido Schimmel
2022-03-21 17:51 ` [PATCH net-next 2/2] selftests: forwarding: Use same VRF for port and VLAN upper Ido Schimmel
2022-03-21 17:53 ` Ido Schimmel [this message]
2022-03-21 18:06 ` [PATCH net-next 0/2] selftests: forwarding: Locked bridge port fixes Jakub Kicinski
2022-03-22 11:10 ` patchwork-bot+netdevbpf
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=Yji7s4qjjEy/SSXx@shredder \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=schultz.hans@gmail.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).