From: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
To: Taras Chornyi <tchornyi@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/4] net: marvell: prestera: rework bridge flags setting
Date: Mon, 23 May 2022 18:56:26 +0000 [thread overview]
Message-ID: <GV1P190MB2019161DB961FE1EC006C478E4D49@GV1P190MB2019.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220523184439.5567-2-oleksandr.mazur@plvision.eu>
> Subject: [PATCH net-next 1/4] net: marvell: prestera: rework bridge flags setting
> This patch series adds support for the MDB handling for the marvell
> Prestera Driver. It's used to propagate IGMP groups registered within
> the Kernel to the underlying HW (offload registered groups).
...
Please ignore this particular patchset series as it's incomplete - i've sent it to public by mistake, and will send an
actual - V2 - complete patch-series that was meant to be sent out into public;
I've had a script that added receipents automatically by mistake, as it was meant to be a test-out mail;
next prev parent reply other threads:[~2022-05-23 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220523184439.5567-1-oleksandr.mazur@plvision.eu>
2022-05-23 18:44 ` [PATCH net-next 1/4] net: marvell: prestera: rework bridge flags setting Oleksandr Mazur
2022-05-23 18:56 ` Oleksandr Mazur [this message]
2022-05-23 19:10 ` Jakub Kicinski
2022-05-23 18:44 ` [PATCH net-next 2/4] net: marvell: prestera: define MDB/flood domain entries and HW API to offload them to the HW Oleksandr Mazur
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=GV1P190MB2019161DB961FE1EC006C478E4D49@GV1P190MB2019.EURP190.PROD.OUTLOOK.COM \
--to=oleksandr.mazur@plvision.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tchornyi@marvell.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).