netdev - Re: [PATCH v2 net-next] tc: remove unused redirect ttl

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:	Fri, 1 May 2015 13:33:28 -0700
From:	Cong Wang <cwang@...pensource.com>
To:	Alexei Starovoitov <ast@...mgrid.com>
Cc:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
	"David S. Miller" <davem@...emloft.net>,
	Jamal Hadi Salim <jhs@...atatu.com>,
	Daniel Borkmann <daniel@...earbox.net>,
	Florian Westphal <fw@...len.de>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 net-next] tc: remove unused redirect ttl

On Fri, May 1, 2015 at 10:28 AM, Alexei Starovoitov <ast@...mgrid.com> wrote:
> I don't think that's how it works. I've applied Jamal's patch
> then fixed few minor things. Therefore his SOB is on top and
> mine below. 'From' has no DCO meaning. It's used from time to time
> in merge request summary, but that's a different case.


Quote from Documentation/SubmittingPatches:

"
The "from" line must be the very first line in the message body,
and has the form:

        From: Original Author <author@...mple.com>

The "from" line specifies who will be credited as the author of the
patch in the permanent changelog.  If the "from" line is missing,
then the "From:" line from the email header will be used to determine
the patch author in the changelog.
"

You should take a look at how Andrew Morton works
when he fixes minor things, I am sure he fixes much
more than you do.
--
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