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-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 25 Aug 2020 13:31:16 +0100
From:   Daniel Stone <>
To:     Mauro Carvalho Chehab <>
Cc:     Dave Airlie <>,
        Neil Armstrong <>,
        David Airlie <>,
        Wanchun Zheng <>,, dri-devel <>,
        Andrzej Hajda <>,
        Laurent Pinchart <>,
        Sam Ravnborg <>,
        driverdevel <>,
        Daniel Borkmann <>,
        John Fastabend <>,
        Xiubin Zhang <>,
        Wei Xu <>,
        Xinliang Liu <>,
        Xinwei Kong <>,
        Tomi Valkeinen <>,
        Bogdan Togorean <>,
        Jakub Kicinski <>,
        Laurentiu Palcu <>,
        linux-media <>,
        <>, Liwei Cai <>,
        Jesper Dangaard Brouer <>,
        Manivannan Sadhasivam <>,
        Chen Feng <>,
        Alexei Starovoitov <>,
        "moderated list:DMA BUFFER SHARING FRAMEWORK" 
        <>, Rob Herring <>,, Rob Clark <>,
        linux-arm-kernel <>,
        Greg Kroah-Hartman <>,
        lkml <>,
        Liuyao An <>,
        Network Development <>,
        Rongrong Zou <>,
        BPF Mailing List <>,
        "David S. Miller" <>
Subject: Re: [PATCH 00/49] DRM driver for Hikey 970

Hi Mauro,

On Tue, 25 Aug 2020 at 12:30, Mauro Carvalho Chehab
<> wrote:
> Sorry, but I can't agree that review is more important than to be able
> to properly indicate copyrights in a valid way at the legal systems that
> it would apply ;-)

The way to properly indicate copyright coverage is to insert a
copyright statement in the file. This has been the accepted way of
communicating copyright notices since approximately the dawn of time.
The value of the 'author' field within a chain of git commits does not
have privileged legal value.

If what you were saying is true, it would be impossible for any
project to copy code from any other project, unless they did git
filter-branch and made sure to follow renames too. As others have
noted, it would also be impossible for any patches to be developed
collaboratively by different copyright holders, or for maintainers to
apply changes.

This is accepted community practice and has passed signoffs from a
million different lawyers and copyright holders. If you wish to break
with this and do something different, the onus is on you to provide
the community with _specific_ legal advice; if this is accepted, the
development model would have to drastically change in the presence of
single pieces of code developed by multiple distinct copyright


Powered by blists - more mailing lists