netdev - Re: [PATCH net-next]r8169:Correct size from dma_alloc_coherent Maximum size register with size argument from dma_alloc_coherent old variable R8169_RX_RING_BYTES return to much value 17000 instead of value of rx_buf_sz, another issue is on rtl8169_init_ring func, Tx buffer and Rx buffer have same number off descriptors NUM_RX

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:	Sun, 26 Jul 2015 15:55:47 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	corcodel.marian@...il.com
Cc:	netdev@...r.kernel.org, romieu@...zoreil.com
Subject: Re: [PATCH net-next]r8169:Correct size from dma_alloc_coherent
 Maximum size register with size argument from dma_alloc_coherent old
 variable R8169_RX_RING_BYTES return to much value 17000 instead of value
 of rx_buf_sz, another issue is on rtl8169_init_ring func, Tx buffer and Rx
 buffer have same number off descriptors NUM_RX_DESC, not others values.

This, again, is improperly submitted.

Again, your entire commit message is in the subject line and this is
not what we want.

This constant wave of badly formed patch submissions is extremely
frustrating, and whether you realise it or not your improper
submissions are consuming a large amount of valuable developer time.
--
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