From: David Miller <davem@davemloft.net>
To: nicolas.ferre@atmel.com
Cc: netdev@vger.kernel.org, havard@skinnemoen.net,
bhutchings@solarflare.com, linux-arm-kernel@lists.infradead.org,
plagnioj@jcrosoft.com, patrice.vilchez@atmel.com,
linux-kernel@vger.kernel.org, manabian@gmail.com,
David.Laight@ACULAB.COM
Subject: Re: [PATCH v4 00/10] net/macb: driver enhancement concerning GEM support, ring logic and cleanup
Date: Thu, 01 Nov 2012 11:46:42 -0400 (EDT) [thread overview]
Message-ID: <20121101.114642.1433440763058405336.davem@davemloft.net> (raw)
In-Reply-To: <cover.1351690694.git.nicolas.ferre@atmel.com>
From: Nicolas Ferre <nicolas.ferre@atmel.com>
Date: Wed, 31 Oct 2012 17:04:49 +0100
> 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.
> Newer pinctrl infrastructure support is added but it is optional.
>
> The series has been tested on several Atmel AT91 SoC with the two MACB/GEM
> flavors.
>
> v4: - remove unneeded device tree header includes
> - modified the computation of available entries in ring buffer
> v3: - rebased on net-next to take into account current effor to merge
> at91_ether with macb drivers
> - add additional patch to use the new pinctrl infrastructure
> v2: - modify the tx error handling: now uses a workqueue
> - information provided by ethtool -i were not accurate: removed
Series applied to net-next
prev parent reply other threads:[~2012-11-01 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 16:04 [PATCH v4 00/10] net/macb: driver enhancement concerning GEM support, ring logic and cleanup Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 01/10] net/macb: Add support for Gigabit Ethernet mode Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 02/10] net/macb: memory barriers cleanup Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 03/10] net/macb: change debugging messages Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 04/10] net/macb: remove macb_get_drvinfo() Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 05/10] net/macb: tx status is more than 8 bits now Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 06/10] net/macb: clean up ring buffer logic Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 07/10] net/macb: ethtool interface: add register dump feature Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 08/10] net/macb: better manage tx errors Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 09/10] net/macb: Offset first RX buffer by two bytes Nicolas Ferre
2012-10-31 16:04 ` [PATCH v4 10/10] net/macb: add pinctrl consumer support Nicolas Ferre
2012-11-01 14:47 ` [PATCH v4 00/10] net/macb: driver enhancement concerning GEM support, ring logic and cleanup Jean-Christophe PLAGNIOL-VILLARD
2012-11-01 15:46 ` David Miller [this message]
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=20121101.114642.1433440763058405336.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=bhutchings@solarflare.com \
--cc=havard@skinnemoen.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=patrice.vilchez@atmel.com \
--cc=plagnioj@jcrosoft.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).