[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiHJaHHh-GYV7tG0cLRFZ=TB0r-na3Htsqgw6H6D5ytHg@mail.gmail.com>
Date: Tue, 1 Mar 2016 22:48:58 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: David Miller <davem@...emloft.net>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
Linux Netdev List <netdev@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Eran Ben Elisha <eranbe@...lanox.com>,
"talal@...lanox.com" <talal@...lanox.com>,
Majd Dibbiny <majd@...lanox.com>, Amir Vadai <amir@...ai.me>
Subject: Re: [PATCH net-next V2 0/9] mlx5 driver updates
On Tue, Mar 1, 2016 at 9:51 PM, David Miller <davem@...emloft.net> wrote:
[...]
> I'm not going to allow two sets of parallel sets of changes to
> one driver you guys maintain to be submitted at once.
[...]
> Get one of these accepted first, then you can submit the other one.
> I'm tossing all of these changes, resubmit the one you want to be
> applied first.
Dave,
Point taken. I thought that since Amir's changes are dealing with
TC/flower offloads along with driver support, it's okay to submit that
in parallel for frequent driver updates that don't deal with core
networking stuff, and I was wrong :(
Saeed will re-submit his series and Amir's will wait for that one to
be accepted before he sends V1.
Or.
Powered by blists - more mailing lists