From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org, ogerlitz@mellanox.com,
talal@mellanox.com, eranbe@mellanox.com
Subject: Re: [PATCH net-next V1 00/12] Mellanox 100G ethernet SRIOV Upgrades
Date: Tue, 03 May 2016 12:18:45 -0400 (EDT) [thread overview]
Message-ID: <20160503.121845.38810507805302539.davem@davemloft.net> (raw)
In-Reply-To: <20160503.121254.1213266710265417601.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Tue, 03 May 2016 12:12:54 -0400 (EDT)
>
> Please don't have two patch series pending for the same driver (mlx5) and
> the same tree (net-next).
>
> This makes things extremely confusing (is patch set #2 dependent upon #1?
> what if I ask for changes to patch set #1?).
>
> So always let the first patch series get fully resolved before sending
> the second series.
>
> I'm tossing this series out.
Sorry, I just realized this is a new version of the previous series.
What confused me is "V1", because this isn't "V1". Please don't number
things like that.
The first posting is implicitly "V1" and any subsequent version is
therefore "v2", "v3", and so on.
Thanks.
next prev parent reply other threads:[~2016-05-03 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 14:13 [PATCH net-next V1 00/12] Mellanox 100G ethernet SRIOV Upgrades Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 01/12] net/mlx5e: Fix aRFS compilation dependency Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 02/12] net/mlx5: Flow steering, Add vport ACL support Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 03/12] net/mlx5: E-Switch, Replace vport spin lock with synchronize_irq() Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 04/12] net/mlx5: E-Switch, Fix error flow memory leak Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 05/12] net/mlx5: E-Switch, Introduce VST vport ingress/egress ACLs Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 06/12] net/mlx5: E-Switch, Vport ingress/egress ACLs rules for VST mode Saeed Mahameed
2016-05-03 14:13 ` [PATCH net-next V1 07/12] net/mlx5: E-Switch, Vport ingress/egress ACLs rules for spoofchk Saeed Mahameed
2016-05-03 14:14 ` [PATCH net-next V1 08/12] net/mlx5: E-Switch, Enable/disable ACL tables on demand Saeed Mahameed
2016-05-03 14:14 ` [PATCH net-next V1 09/12] net/mlx5: E-Switch, Use vport event handler for vport cleanup Saeed Mahameed
2016-05-03 14:14 ` [PATCH net-next V1 10/12] net/mlx5: E-Switch, Add promiscuous and allmulti FDB flowtable groups Saeed Mahameed
2016-05-03 14:14 ` [PATCH net-next V1 11/12] net/mlx5: E-Switch, Implement promiscuous rx modes vf request handling Saeed Mahameed
2016-05-03 14:14 ` [PATCH net-next V1 12/12] net/mlx5: E-Switch, Implement trust vf ndo Saeed Mahameed
2016-05-03 16:12 ` [PATCH net-next V1 00/12] Mellanox 100G ethernet SRIOV Upgrades David Miller
2016-05-03 16:18 ` David Miller [this message]
2016-05-03 16:28 ` Saeed Mahameed
2016-05-03 16:20 ` Saeed Mahameed
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=20160503.121845.38810507805302539.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eranbe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=talal@mellanox.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).