All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Cc: Taras Chornyi <tchornyi@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"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 12:10:41 -0700	[thread overview]
Message-ID: <20220523121041.3919affc@kernel.org> (raw)
In-Reply-To: <GV1P190MB2019161DB961FE1EC006C478E4D49@GV1P190MB2019.EURP190.PROD.OUTLOOK.COM>

On Mon, 23 May 2022 18:56:26 +0000 Oleksandr Mazur wrote:
> > 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;

Please note that net-next is closed for the next two weeks tho:

http://vger.kernel.org/~davem/net-next.html

  reply	other threads:[~2022-05-23 19:30 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
2022-05-23 19:10     ` Jakub Kicinski [this message]
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=20220523121041.3919affc@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleksandr.mazur@plvision.eu \
    --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 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.