linux-kernel - Re: [PATCH v3 5/5] staging: et131x: update TODO list

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Nov 2013 21:20:06 +0000
From:	Mark Einon <mark.einon@...il.com>
To:	ZHAO Gang <gamerh2o@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH v3 5/5] staging: et131x: update TODO list

On Wed, Nov 20, 2013 at 03:58:37PM +0800, ZHAO Gang wrote:
> remove items that have been done
> 
> Signed-off-by: ZHAO Gang <gamerh2o@...il.com>

If the two small issues in patch 1/5 are fixed:

Acked-by: Mark Einon <mark.einon@...il.com>

> ---
>  drivers/staging/et131x/README | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/drivers/staging/et131x/README b/drivers/staging/et131x/README
> index 8da96a6..00a34ea 100644
> --- a/drivers/staging/et131x/README
> +++ b/drivers/staging/et131x/README
> @@ -11,12 +11,7 @@ TODO:
>  	- Look at reducing the number of spinlocks
>  	- Simplify code in nic_rx_pkts(), when determining multicast_pkts_rcvd
>  	- Implement NAPI support
> -	- In et131x_tx(), don't return NETDEV_TX_BUSY, just drop the packet with kfree_skb().
>  	- Reduce the number of split lines by careful consideration of variable names etc.
> -	- Do this in et131x.c:
> -                struct fbr_lookup *fbr;
> -                fbr = rx_local->fbr[id];
> -	  Then replace all the instances of "rx_local->fbr[id]" with fbr.
>  
>  Please send patches to:
>  	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> -- 
> 1.8.3.1
> 
--
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/