From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Claudiu Manoil <claudiu.manoil@freescale.com>
Cc: <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v1 0/7] Fix, cleanup, optimize gfar_private and the Rx path
Date: Thu, 14 Feb 2013 11:49:45 -0500 [thread overview]
Message-ID: <511D15A9.9090001@windriver.com> (raw)
In-Reply-To: <1360854007-11094-1-git-send-email-claudiu.manoil@freescale.com>
On 13-02-14 10:00 AM, Claudiu Manoil wrote:
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
> "David S. Miller" <davem@davemloft.net>
>
>
> Hi Dave,
> These patches went already through a review round with Paul.
> Changes since the initial version of the patches:
> * split the 1st patch into two patches (01 & 02, as suggested by Paul)
> * added the suggested trivial cleanup patch:
> gianfar: gfar_process_frame returns void
> * provided "long logs" with detailed comments and explanations
The commit headers do look a lot better, thanks. Passes basic boot
test on today's net-next with sbc8548 and NFS root.
Paul.
--
>
> Thank you.
>
> Regards,
> Claudiu
>
>
> Claudiu Manoil (7):
> gianfar: Remove unused device_node ref in gfar_private
> gianfar: Add device ref (dev) in gfar_private
> gianfar: Cleanup and optimize struct gfar_private
> gianfar: GRO_DROP is unlikely
> gianfar: gfar_process_frame returns void
> gianfar: Remove wrong buffer size conditioning to VLAN h/w offload
> gianfar: Fix and cleanup Rx FCB indication
>
> drivers/net/ethernet/freescale/gianfar.c | 85 ++++++++++++---------------
> drivers/net/ethernet/freescale/gianfar.h | 96 +++++++++++++++--------------
> 2 files changed, 88 insertions(+), 93 deletions(-)
>
next prev parent reply other threads:[~2013-02-14 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 15:00 [PATCH net-next v1 0/7] Fix, cleanup, optimize gfar_private and the Rx path Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 1/7] gianfar: Remove unused device_node ref in gfar_private Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 2/7] gianfar: Add device ref (dev) " Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 3/7] gianfar: Cleanup and optimize struct gfar_private Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 4/7] gianfar: GRO_DROP is unlikely Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 5/7] gianfar: gfar_process_frame returns void Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 6/7] gianfar: Remove wrong buffer size conditioning to VLAN h/w offload Claudiu Manoil
2013-02-14 15:00 ` [PATCH net-next 7/7] gianfar: Fix and cleanup Rx FCB indication Claudiu Manoil
2013-02-14 16:49 ` Paul Gortmaker [this message]
2013-02-14 18:32 ` [PATCH net-next v1 0/7] Fix, cleanup, optimize gfar_private and the Rx path David Miller
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=511D15A9.9090001@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=claudiu.manoil@freescale.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.