netdev - [PATCH net-next v1 0/7] Fix, cleanup, optimize gfar

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1360854007-11094-1-git-send-email-claudiu.manoil@freescale.com>
Date:	Thu, 14 Feb 2013 17:00:00 +0200
From:	Claudiu Manoil <claudiu.manoil@...escale.com>
To:	<netdev@...r.kernel.org>
CC:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: [PATCH net-next v1 0/7] Fix, cleanup, optimize gfar_private and the Rx path

Cc: Paul Gortmaker <paul.gortmaker@...driver.com>,
  "David S. Miller" <davem@...emloft.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

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(-)

-- 
1.7.7.4


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html