linux-kernel - Re: [PATCH v3 3/4] sta2x11_vip: convert to videobuf2 and control framework

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: <50BF4E25.3010207@redhat.com>
Date:	Wed, 05 Dec 2012 11:37:41 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Federico Vaga <federico.vaga@...il.com>
CC:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Pawel Osciak <pawel@...iak.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Hans Verkuil <hans.verkuil@...co.com>,
	Giancarlo Asnaghi <giancarlo.asnaghi@...com>,
	linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v3 3/4] sta2x11_vip: convert to videobuf2 and control
 framework

Em 05-12-2012 11:27, Federico Vaga escreveu:
>>> Ok, I understand. I will write something like this.
>>>
>>>    * Copyright (C) 2012       ST Microelectronics
>>>    *      author: Federico Vaga <federico.vaga@...il.com>
>>>    * Copyright (C) 2010       WindRiver Systems, Inc.
>>>    *      authors: Andreas Kies <andreas.kies@...driver.com>
>>>    *               Vlad Lungu <vlad.lungu@...driver.com>
>>
>> Sounds perfect to me.
>
> I will answer to this with a patch

Thanks!

>> As you said, the best place to discuss about it is likely at LKML.
>> [...]
>> Btw, this is why it is called "git blame", and not "git authorship":
>> it is a tool to identify who was the last one that modified the code.
>> Its main usage is to identify who might have introduced a bug on the
>> code.
>
> I know I know, it was just a stupid example to expose the problem that I have
> in my mind. I know that it is very difficult (impossible?) to assign the
> authorship of a single line, and git blame it is not the tool to do this :)
>
> I think you understand what I mean despite the stupid example

Yeah, I hear you.

Not sure if you got my point: the main point of removing MODULE_AUTHOR
and other copyright stuff is that such patch may easily be doing something
that could be considered a copyright violation, being bad not only to
the affected driver, but to the entire Kernel.

So, we need to handle it with due care. Getting other authors's
acks on such patch seems to be the only safe way of doing that.

Regards,
Mauro

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/