All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>,
	Roopa Prabhu <roopa@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [Bridge] [PATCH 1/1 net-next] net: bridge: add support for host l2 mdb entries
Date: Thu, 24 Feb 2022 14:59:10 +0100	[thread overview]
Message-ID: <878ru0qsb5.fsf@gmail.com> (raw)
In-Reply-To: <66dc205f-9f57-61c1-35d9-8712e8d9fe3a@blackwall.org>

On Thu, Feb 24, 2022 at 13:26, Nikolay Aleksandrov <razor@blackwall.org> wrote:
> On 23/02/2022 19:24, Joachim Wiberg wrote:
>> This patch expands on the earlier work on layer-2 mdb entries by adding
>> support for host entries.
> It would be nice to add a selftest for L2 entries. You can send it as a follow-up.

OK, will do!  It's on my immediate backlog.

Thanks
 /Joachim
 

WARNING: multiple messages have this Message-ID (diff)
From: Joachim Wiberg <troglobit@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>,
	Roopa Prabhu <roopa@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 1/1 net-next] net: bridge: add support for host l2 mdb entries
Date: Thu, 24 Feb 2022 14:59:10 +0100	[thread overview]
Message-ID: <878ru0qsb5.fsf@gmail.com> (raw)
In-Reply-To: <66dc205f-9f57-61c1-35d9-8712e8d9fe3a@blackwall.org>

On Thu, Feb 24, 2022 at 13:26, Nikolay Aleksandrov <razor@blackwall.org> wrote:
> On 23/02/2022 19:24, Joachim Wiberg wrote:
>> This patch expands on the earlier work on layer-2 mdb entries by adding
>> support for host entries.
> It would be nice to add a selftest for L2 entries. You can send it as a follow-up.

OK, will do!  It's on my immediate backlog.

Thanks
 /Joachim
 

  reply	other threads:[~2022-02-24 13:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 17:24 [Bridge] [PATCH 1/1 net-next] net: bridge: add support for host l2 mdb entries Joachim Wiberg
2022-02-23 17:24 ` Joachim Wiberg
2022-02-24 11:26 ` [Bridge] " Nikolay Aleksandrov
2022-02-24 11:26   ` Nikolay Aleksandrov
2022-02-24 13:59   ` Joachim Wiberg [this message]
2022-02-24 13:59     ` Joachim Wiberg
2022-02-24 16:06   ` [Bridge] " Jakub Kicinski
2022-02-24 16:06     ` Jakub Kicinski
2022-02-24 16:29     ` [Bridge] " Joachim Wiberg
2022-02-24 16:29       ` Joachim Wiberg
2022-02-24 16:48       ` [Bridge] " Jakub Kicinski
2022-02-24 16:48         ` Jakub Kicinski
2022-02-24 17:27         ` [Bridge] " Joachim Wiberg
2022-02-24 17:27           ` Joachim Wiberg
2022-04-11  8:40 ` [Bridge] [PATCH v2 net-next 0/2] " Joachim Wiberg
2022-04-11  8:40   ` Joachim Wiberg
2022-04-11  8:40   ` [Bridge] [PATCH v2 net-next 1/2] " Joachim Wiberg
2022-04-11  8:40     ` Joachim Wiberg
2022-04-11  8:40   ` [Bridge] [PATCH v2 net-next 2/2] selftests: forwarding: new test, verify host " Joachim Wiberg
2022-04-11  8:40     ` Joachim Wiberg
2022-04-12  8:30   ` [Bridge] [PATCH v2 net-next 0/2] net: bridge: add support for host l2 " patchwork-bot+netdevbpf
2022-04-12  8:30     ` 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=878ru0qsb5.fsf@gmail.com \
    --to=troglobit@gmail.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.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 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.