netdev - Re: [PATCH net-next] r8169:Set RxConfig on same func. with TxConfig

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:	Tue, 18 Aug 2015 12:42:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	corcodel.marian@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] r8169:Set RxConfig on same func. with TxConfig

From: Corcodel Marian <corcodel.marian@...il.com>
Date: Tue, 18 Aug 2015 22:10:21 +0300

>  Add set DMA burst size and  Rx FIFO threshold on RxConfig  
>   register to function rtl_set_rx_tx_config_register.
> 
> 
> Signed-off-by: Corcodel Marian <corcodel.marian@...il.com>

I would like to politely ask you to stop submitting these r8169 patches
right now.

Your method of handling your patch submissions is not acceptable and
is scarily wasting developer resources every single day.

When people give you feedback about why your patch is not correct, or
ask you questions, you often do not respond.  Or, if you do respond,
you give a very small response that do not actually answer the
question given to you.

When people give feedback to your patch, you _MUST_ engage in a
coherent full conversation with the person giving you feedback.

It is not acceptable to just ignore what that person tells you,
or to be quiet.  You cannot just keep throwing patches blindly
to this mailing list.

It is especially not acceptable to ignore feedback, and then keep
submitting more and more patches.  This is the worst thing in the
world that you can do.

You are creating a situation where the people trying to help you by
reviewing your work feel like they are wasting their time.

Furthermore, you haven't answered the most basic question we have
asked you.  Where are all of these r1869 patches coming from?  What is
the reason why you are looking into all of the r8169 issues all of a
sudden?  It looks very random and strange to all of us.

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