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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 22 Mar 2019 14:11:35 -0700
From:   Sean Christopherson <>
To:     Jonathan Corbet <>,
        Andy Whitcroft <>,
        Joe Perches <>
        "Tobin C . Harding" <>,
        Thomas Gleixner <>,
        Jani Nikula <>,
        Jorge Ramirez-Ortiz <>,
        Jonathan Cameron <>,
        Greg Kroah-Hartman <>,
        Niklas Cassel <>
Subject: [PATCH v5 0/2] docs: checkpatch: improve handling of Co-developed-by

The recently introduced Co-developed-by: tag has seen a spate of
improper usage, likely because the tag is less intuitive and slightly
more complex than most other tags.  Rework the documentation to be more
explicit in how Co-developed-by: is intended to be used, add examples
in the docs, and add logic to checkpatch to reinforce proper usage.

    Rewrite the blurb to state standard sign-off procedure should be
    followed as opposed to dictating the original author's SOB be last.
    Update a similar blurb in Documentation/process/5.Posting.rst
    Rework the blurbs to avoid use of the word "original" [Tobin]
v5: Add checkpatch warnings [Joe]
    Fix a spelling error [Niklas]

Sean Christopherson (2):
  docs: Clarify the usage and sign-off requirements for Co-developed-by
  checkpatch: Warn on improper usage of Co-developed-by

 Documentation/process/5.Posting.rst          | 10 +++--
 Documentation/process/submitting-patches.rst | 40 +++++++++++++++++---
 scripts/                        | 18 +++++++++
 3 files changed, 59 insertions(+), 9 deletions(-)


Powered by blists - more mailing lists