[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240726082751.74d349dc@windsurf>
Date: Fri, 26 Jul 2024 08:27:51 +0200
From: Thomas Petazzoni <thomas.petazzoni@...tlin.com>
To: Alex Lanzano <lanzano.alex@...il.com>
Cc: mehdi.djait@...tlin.com, David Airlie <airlied@...il.com>, Daniel Vetter
<daniel@...ll.ch>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann
<tzimmermann@...e.de>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Mehdi Djait <mehdi.djait.k@...il.com>
Subject: Re: [PATCH 0/2] Add driver for Sharp Memory LCD
Hello,
On Thu, 25 Jul 2024 20:07:01 -0400
Alex Lanzano <lanzano.alex@...il.com> wrote:
> What would be the best way to go about doing this? I'm guessing appending to
> MODULE_AUTHOR and adding a Signed-of-by or Co-Developed-by?
Depends on how much you've changed things compared to Mehdi's version.
If you've mostly kept what Mehdi did, then I guess you should keep him
as the author of the commits (i.e the Author: field of the git commit +
the first Signed-off-by), and add your Signed-off-by underneath.
If you've made very significant changes to the point where the code
isn't really Mehdi's code anymore, but just inspired, then you should
set yourself as the author (Author: field of the git commit + the first
Signed-off-by), and credit Mehdi via a Co-developed-by: tag.
In any case, thanks a lot for this pushing this work, much appreciated!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
Powered by blists - more mailing lists