[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160406.235804.2223760831702758803.davem@davemloft.net>
Date: Wed, 06 Apr 2016 23:58:04 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: troy.kisky@...ndarydevices.com
Cc: netdev@...r.kernel.org, fugang.duan@....com, lznuaa@...il.com,
fabio.estevam@....com, l.stach@...gutronix.de, andrew@...n.ch,
tremyfr@...il.com, gerg@...inux.org,
linux-arm-kernel@...ts.infradead.org, johannes@...solutions.net,
stillcompiling@...il.com, sergei.shtylyov@...entembedded.com,
arnd@...db.de
Subject: Re: [PATCH net-next V3 00/16] net: fec: cleanup and fixes
From: Troy Kisky <troy.kisky@...ndarydevices.com>
Date: Wed, 6 Apr 2016 18:09:17 -0700
> On 4/6/2016 2:20 PM, David Miller wrote:
>>
>> This is a way too large patch series.
>>
>> Please split it up into smaller, more logical, pieces.
>>
>> Thanks.
>>
>
> If you apply the 1st 3 that have been acked, I'll be at 13.
>
> Would I then send the next 5 for V4, and when that is applied
> send another V4 with the next 8 that have been already been acked?
What other reasonable option is there? I can't think of any.
Powered by blists - more mailing lists