From: Ben Hutchings <ben@decadent.org.uk>
To: linux-kernel@vger.kernel.org, linux-firmware@kernel.org
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: [PATCH linux-firmware] LICENCE.siano: Add copyright years
Date: Mon, 5 Dec 2016 04:11:05 +0000 [thread overview]
Message-ID: <20161205041105.GO2697@decadent.org.uk> (raw)
In-Reply-To: <20161203192815.79192463@vento.lan>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
A copyright notice is supposed to specify the years the work was
created.
Mauro Carvalho Chehab <mchehab@infradead.org> writes:
> The oldest copyright I found for the Siano Linux driver is 2005, as
> you can see at:
> drivers/media/common/siano/smscoreapi.c
>
> As the driver talks with the Siano firmware, it has to be written
> before or together with the driver.
>
> Browsing at the new, that seems to match the oldest news about the
> first chipset supported by the driver (sms1000) is from 2006:
> http://www.businesswire.com/news/home/20061206005282/en/Siano-SMS1000-Mobile-Digital-TV-Receiver-Chip
>
> This driver supports both the sms1xx and the newer sms27xx
> chipsets. Due to that, the Rio firmware (ISDB-T) s probably newer,
> as it support only the sms27xx chips, but it could be based on the
> DVB-T firmware.
>
> So, if you really want to put some timestamp, except if someone
> at either Siano or Hauppauge could tell us otherwise, I would stick
> with a copyright notice starting from 2005, going u to the year that
> they got merged at the firmware tree (as some changes might have
> happened until the final version).
So I'm specifying 2005-2014.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
LICENCE.siano | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/LICENCE.siano b/LICENCE.siano
index c100136b585e..97e54402efc3 100644
--- a/LICENCE.siano
+++ b/LICENCE.siano
@@ -1,6 +1,6 @@
FIRMWARE LICENSE TERMS
-Copyright (c) Siano Mobile Silicon Ltd.
+Copyright (c) 2005-2014 Siano Mobile Silicon Ltd.
All rights reserved.
Redistribution. Redistribution and use in binary form, without
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next parent reply other threads:[~2016-12-05 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161203192815.79192463@vento.lan>
2016-12-05 4:11 ` Ben Hutchings [this message]
2016-12-05 9:12 ` [PATCH linux-firmware] LICENCE.siano: Add copyright years Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161205041105.GO2697@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).