[lkml]   [2012]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v3 3/4] sta2x11_vip: convert to videobuf2 and control framework
    Hi Federico,

    Em 04-12-2012 23:12, Federico Vaga escreveu:
    > On Tuesday 04 December 2012 14:15:15 Mauro Carvalho Chehab wrote:
    >> Em 24-09-2012 07:58, Federico Vaga escreveu:
    >>> This patch re-write the driver and use the videobuf2
    >>> interface instead of the old videobuf. Moreover, it uses also
    >>> the control framework which allows the driver to inherit
    >>> controls from its subdevice (ADV7180)
    >>> Signed-off-by: Federico Vaga <>
    >>> Acked-by: Giancarlo Asnaghi <>
    >>> [..........]
    >>> /*
    >>> * This is the driver for the STA2x11 Video Input Port.
    >>> *
    >>> + * Copyright (C) 2012 ST Microelectronics
    >>> * Copyright (C) 2010 WindRiver Systems, Inc.
    >>> *
    >>> * This program is free software; you can redistribute it and/or modify
    >>> it
    >>> @@ -19,36 +20,30 @@
    >>> * The full GNU General Public License is included in this distribution
    >>> in
    >>> * the file called "COPYING".
    >>> *
    >>> - * Author: Andreas Kies <>
    >>> - * Vlad Lungu <>
    >> Why are you dropping those authorship data?
    >> Ok, it is clear to me that most of the code there got rewritten, and,
    >> while IANAL, I think they still have some copyrights on it.
    >> So, if you're willing to do that, you need to get authors ack
    >> on such patch.
    > I re-write the driver, and also the first version of the driver has many
    > modification made by me, many bug fix, style review, remove useless code.
    > The first time I didn't add myself as author because the logic of the driver
    > did not change. This time, plus the old change I think there is nothing of the
    > original driver because I rewrite it from the hardware manual. Practically, It
    > is a new driver for the same device.

    Yeah, there are many changes there that justifies adding you at its
    authorship, and that's ok. Also, anyone saying the size of your patch
    will recognize your and ST efforts to improve the driver.

    However, as some parts of the code were preserved, dropping the old
    authors doesn't sound right (and can even be illegal, in the light
    of the GPL license). It would be ok, though, if you would be
    changing it to something like:

    Copyright (c) 2010 by ...
    Original driver from ...

    or some other similar wording that would preserve their names
    there. We do that even when something is rewritten, like, for
    example, drivers/media/v4l2-core/videobuf-core.c:

    * (c) 2007 Mauro Carvalho Chehab, <>
    * Highly based on video-buf written originally by:
    * (c) 2001,02 Gerd Knorr <>
    * (c) 2006 Mauro Carvalho Chehab, <>
    * (c) 2006 Ted Walther and John Sokol

    > Anyway I will try to contact the original authors for the acked-by.
    >>> MODULE_DESCRIPTION("STA2X11 Video Input Port driver");
    >>> -MODULE_AUTHOR("Wind River");
    >> Same note applies here: we need Wind River's ack on that to drop it.
    > I will try also for this. But I think that this is not a windriver driver
    > because I re-wrote it from the hardware manual. I used the old driver because
    > I thought that it was better than propose a patch that remove the old driver
    > and add my driver.
    > I did not remove the 2010 Copyright from windriver, because they did the job,
    > but this work was paid by ST (copyright 2012) and made completely by me.

    The same reason why you didn't drop windriver's copyright also applies here:
    while most of the code changed, there are still a few things left from the
    original driver.

    > Is my thinking wrong?
    > Just a question for the future so I avoid to redo the same error. If I re-
    > wrote most of a driver I cannot change the authorship automatically without
    > the acked-by of the previous author. If I ask to the previous author and he
    > does not give me the acked-by (or he is unreachable, he change email address),
    > then the driver is written by me but the author is someone else? Right? So, it
    > is better if I propose a patch which remove a driver and a patch which add my
    > driver?

    The only way of not preserving the original authors here were if you
    start from scratch, without looking at the original code (and you can
    somehow, be able to proof it), otherwise, the code will be fit as a
    "derivative work", in the light of GPL, and should be preserving the
    original authorship.

    Something started from scratch like that will hardly be accepted upstream,
    as regressions will likely be introduced, and previously supported
    hardware/features may be lost in the process.

    Of course the original author can abdicate to his rights of keeping his
    name on it. Yet, even if he opt/accept to not keep his name explicitly
    there, his copyrights are preserved, with the help of the git history.

    That's said, no single kernel developer/company has full copyrights on
    any part of the Kernel, as their code are based on someone else's work.
    For example, all Kernel drivers depend on drivers/base, with in turn,
    depends on memory management, generic helper functions, arch code, etc.

    So, IMHO, there's not much point on dropping authorship messages.


     \ /
      Last update: 2012-12-05 13:21    [W:6.327 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site