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]
Message-ID: <alpine.DEB.2.20.1711161301250.2191@nanos>
Date:   Thu, 16 Nov 2017 13:16:30 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     "Sajjan, Vikas C" <vikas.cha.sajjan@....com>
cc:     "rjw@...ysocki.net" <rjw@...ysocki.net>,
        "rafael.j.wysocki@...el.com" <rafael.j.wysocki@...el.com>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "kkamagui@...il.com" <kkamagui@...il.com>,
        "mingo@...nel.org" <mingo@...nel.org>,
        "Lakshminarasimha, Sunil Vishwanathpur" <sunil.vl@....com>,
        "Attar, Abdul Lateef" <abdul-lateef.attar@....com>
Subject: RE: [PATCH v2 1/2] acpi/x86: Fix improper handling of SCI INT for
 platforms supporting only IOAPIC mode

On Thu, 16 Nov 2017, Sajjan, Vikas C wrote:
> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@...utronix.de] 
> Sent: Thursday, November 16, 2017 4:35 PM
> To: Sajjan, Vikas C <vikas.cha.sajjan@....com>
> Cc: rjw@...ysocki.net; rafael.j.wysocki@...el.com; linux-pm@...r.kernel.org; linux-acpi@...r.kernel.org; linux-kernel@...r.kernel.org; kkamagui@...il.com; mingo@...nel.org; Lakshminarasimha, Sunil Vishwanathpur <sunil.vl@....com>; Attar, Abdul Lateef <abdul-lateef.attar@....com>
> Subject: Re: [PATCH v2 1/2] acpi/x86: Fix improper handling of SCI INT for platforms supporting only IOAPIC mode

Can you please fix your mail client to not pointlessly copy the full mail
header?

 On Thu, 16 Nov 2017, Thomas Gleixner wrote:

is enough. The rest is in the real mail headers already.

> On Thu, 16 Nov 2017, Vikas C Sajjan wrote:
> > Signed-off-by: Vikas C Sajjan <vikas.cha.sajjan@....com>
> > Signed-off-by: Sunil V L <sunil.vl@....com>
> > Signed-off-by: Abdul Lateef Attar <abdul-lateef.attar@....com>
> 
> This Signed-off-by chain is broken. It says:
> 
>      Vikas wrote the patch and handed it to Sunil
>      Sunil handed it to Abdul
>      Abdul sent it to lkml
> 
> Which is obviously not the case.

> 3 of us worked on it, hence I had put all the 3 "Signed-off-by". Are you
> suggesting to call-out who did what.  Is that what you mean, when you say
> "Signed-off-by chain is broken".

No. As I explained above. The Signed-off-by is a chain. The first one is
from the author. The following ones are from people who handled,
transported or applied the patch.

See Documentation/process/submitting-patches.rst the chapter:

  Developer's Certificate of Origin 1.1

for further clarification.

Unfortunately we have no canonical way to express joint develoment, but we
have used non formal tags for that, like

     Co-developed-by:

which give credits to the people who were involved in the development.

Thanks,

	tglx


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ