netdev - Re: [PATCH] net: fec: init maximum receive buffer size for ring1 and ring2

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20141124.152250.380142287256307570.davem@davemloft.net>
Date:	Mon, 24 Nov 2014 15:22:50 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	b38611@...escale.com
Cc:	netdev@...r.kernel.org, bhutchings@...arflare.com,
	stephen@...workplumber.org, festevam@...il.com
Subject: Re: [PATCH] net: fec: init maximum receive buffer size for ring1
 and ring2

From: Fugang Duan <b38611@...escale.com>
Date: Sun, 23 Nov 2014 17:23:06 +0800

> i.MX6SX fec support three rx ring1, the current driver lost to init
> ring1 and ring2 maximum receive buffer size, that cause receving
> frame date length error. The driver reports "rcv is not +last" error
> log in user case.
> 
> Signed-off-by: Fugang Duan <B38611@...escale.com>

This patch does not apply to the 'net' tree, although it does
apply cleanly to the net-next tree.

Determining which tree a patch is for is not my job, it is your's.

Therefore you must always explicitly state what tree your patch
is intended to be added to, by starting your Subject line
with "[PATCH net] " or "[PATCH net-next] ".

I've applied this, but next time I will just ask you to properly
submit the patch instead.
--
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