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]
Message-Id: <20170525.163329.1506857538759050908.davem@davemloft.net>
Date:   Thu, 25 May 2017 16:33:29 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     petedaws@...il.com
Cc:     kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
        kaber@...sh.net, stephen@...workplumber.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] ip6_tunnel, ip6_gre: fix setting of DSCP on
 encapsulated packets

From: Peter Dawson <petedaws@...il.com>
Date: Fri, 26 May 2017 06:08:42 +1000

> On Thu, 25 May 2017 15:49:14 -0400 (EDT)
> David Miller <davem@...emloft.net> wrote:
> 
>> Still not correct, you need to use a "Fixes: " tag of the form:
>> 
>> Fixes: 90427ef5d2a4 ("ipv6: fix flow labels when the traffic class is non-0")
>> 
>> And it must appear of the first line of tags, before signoffs and acks,
>> with no empty lines in between.
> 
> Here is my proposed commit message in full. Note that 
> the "Fixes" line extends to 78 chars. Is this OK?

Yes, that looks perfect.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ