From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Amit Cohen <amcohen@nvidia.com>,
<mlxsw@nvidia.com>
Subject: Re: [PATCH net-next 00/17] mlxsw: Support CFF flood mode
Date: Thu, 30 Nov 2023 11:43:47 +0100 [thread overview]
Message-ID: <8734wna5am.fsf@nvidia.com> (raw)
In-Reply-To: <20231129063048.3337bded@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> On Wed, 29 Nov 2023 11:30:27 +0100 Petr Machata wrote:
>> > Is there a reason not to split this series into two?
>>
>> I can do 5 + 12. I'll resend.
>
> It's okay this time, just keep that in mind going forward.
OK, I'll be more careful about the patch limit in the future.
Thanks.
next prev parent reply other threads:[~2023-11-30 10:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 15:50 [PATCH net-next 00/17] mlxsw: Support CFF flood mode Petr Machata
2023-11-28 15:50 ` [PATCH net-next 01/17] mlxsw: spectrum_fid: Privatize FID families Petr Machata
2023-11-28 15:50 ` [PATCH net-next 02/17] mlxsw: spectrum_fid: Rename FID ops, families, arrays Petr Machata
2023-11-28 15:50 ` [PATCH net-next 03/17] mlxsw: spectrum_fid: Split a helper out of mlxsw_sp_fid_flood_table_mid() Petr Machata
2023-11-28 15:50 ` [PATCH net-next 04/17] mlxsw: spectrum_fid: Make mlxsw_sp_fid_ops.setup return an int Petr Machata
2023-11-28 15:50 ` [PATCH net-next 05/17] mlxsw: spectrum_fid: Move mlxsw_sp_fid_flood_table_init() up Petr Machata
2023-11-28 15:50 ` [PATCH net-next 06/17] mlxsw: spectrum_fid: Add an op for flood table initialization Petr Machata
2023-11-28 15:50 ` [PATCH net-next 07/17] mlxsw: spectrum_fid: Add an op to get PGT allocation size Petr Machata
2023-11-28 15:50 ` [PATCH net-next 08/17] mlxsw: spectrum_fid: Add an op to get PGT address of a FID Petr Machata
2023-11-28 15:50 ` [PATCH net-next 09/17] mlxsw: spectrum_fid: Add an op for packing SFMR Petr Machata
2023-11-28 15:50 ` [PATCH net-next 10/17] mlxsw: spectrum_fid: Add a not-UC packet type Petr Machata
2023-11-28 15:50 ` [PATCH net-next 11/17] mlxsw: spectrum_fid: Add hooks for RSP table maintenance Petr Machata
2023-11-28 15:50 ` [PATCH net-next 12/17] mlxsw: spectrum_fid: Add an object to keep flood profiles Petr Machata
2023-11-28 15:50 ` [PATCH net-next 13/17] mlxsw: spectrum_fid: Add profile_id to flood profile Petr Machata
2023-11-28 15:50 ` [PATCH net-next 14/17] mlxsw: spectrum_fid: Initialize flood profiles in CFF mode Petr Machata
2023-11-28 15:50 ` [PATCH net-next 15/17] mlxsw: spectrum_fid: Add a family for bridge FIDs in CFF flood mode Petr Machata
2023-11-28 15:50 ` [PATCH net-next 16/17] mlxsw: spectrum_fid: Add support for rFID family " Petr Machata
2023-11-28 15:50 ` [PATCH net-next 17/17] mlxsw: spectrum: Use CFF mode where available Petr Machata
2023-11-29 4:02 ` [PATCH net-next 00/17] mlxsw: Support CFF flood mode Jakub Kicinski
2023-11-29 10:30 ` Petr Machata
2023-11-29 14:30 ` Jakub Kicinski
2023-11-30 10:43 ` Petr Machata [this message]
2023-11-30 4: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=8734wna5am.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).