netdev - Re: [PATCH net-next]r8169:Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09. Disable advertise full duplex on chip id RTL_GIGA_MAC_VER_09 wich support random full duplex.(very sad) On branch master Your branch is ahead of 'origin/master' by 18 commits. (use "git push" to publish your local commits)

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

Date:	Sat, 18 Jul 2015 22:21:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	corcodel.marian@...il.com
Cc:	netdev@...r.kernel.org, asu@...-168-0-3.rdsnet.ro
Subject: Re: [PATCH net-next]r8169:Disable advertise full duplex on chip id
 RTL_GIGA_MAC_VER_09. Disable advertise full duplex on chip id
 RTL_GIGA_MAC_VER_09 wich support random full duplex.(very sad) On branch
 master Your branch is ahead of 'origin/master' by 18 commits. (use "git
 push" to publish your local commits)

This is still ver far from acceptable.  You aren't even talking to us when
we ask you questions and ask you to make changes, you just make another
improperly formatted submission of a bad patch all over again.

Your entire description is in your Subject line, and it insufficiently
describes your change.

Frankly, I am very sick and tired of these low quality submissions.  I want to
know where these changes are coming from, who they are important to, and most
importantly why it is so difficult for you to submit your changes properly.

Just simply _LOOK_ at postings by other developers who submit changes
that successfully get accepted by us.

_LOOK_ at how their Subject line looks, and mimick what they do _EXACTLY_

_LOOK_ at how their commit messages look, how detailed they are, how
descriptive they are, and how they are formatted and composed, and
mimick _EACTLY_ what they are doing.

This isn't rocket science, if you want us to take your changes seriously
you _MUST_ learn how to conform to our patch submission methods and
expectations.

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