[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20121026.145938.2087989420370212890.davem@davemloft.net>
Date: Fri, 26 Oct 2012 14:59:38 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nicolas.ferre@...el.com
Cc: manabian@...il.com, netdev@...r.kernel.org, havard@...nnemoen.net,
bhutchings@...arflare.com, linux-arm-kernel@...ts.infradead.org,
plagnioj@...osoft.com, patrice.vilchez@...el.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/9] net/macb: driver enhancement concerning GEM
support, ring logic and cleanup
From: Nicolas Ferre <nicolas.ferre@...el.com>
Date: Fri, 26 Oct 2012 17:25:08 +0200
> David,
>
> On 09/19/2012 01:55 PM, Nicolas Ferre :
>> This is an enhancement work that began several years ago. I try to catchup with
>> some performance improvement that has been implemented then by Havard.
>> The ring index logic and the TX error path modification are the biggest changes
>> but some cleanup/debugging have been added along the way.
>> The GEM revision will benefit from the Gigabit support.
>>
>> The series has been tested on several Atmel AT91 SoC with the two MACB/GEM
>> flavors.
>>
>> v2: - modify the tx error handling: now uses a workqueue
>> - information provided by ethtool -i were not accurate: removed
>
> I am about to re-send this patch series. Should I rebase it on top of
> Joachim's recent modifications? I mean, I plan to rebase them on top of
> net-next, is it the proper thing to do?
You should always base your patch on whatever tree you want your patches
applied to.
If you have a dependency on something not in that tree (for example, you
need something in the 'net' tree) you have to tell me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists