All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>,
	Barry Song <Baohua.Song@csr.com>
Subject: Re: [PATCH] serial: sirf: update copyright years to 2014
Date: Wed, 19 Feb 2014 13:16:05 +0800	[thread overview]
Message-ID: <CAGsJ_4wu80_50Vb4tzBT6Uug+JaSgajdTA6N5fK-FtxvCRxxeQ@mail.gmail.com> (raw)
In-Reply-To: <20140214171424.GA26194@kroah.com>

2014-02-15 1:14 GMT+08:00 Greg KH <gregkh@linuxfoundation.org>:
> On Thu, Feb 13, 2014 at 10:27:17AM +0800, Barry Song wrote:
>> 2014-02-13 0:38 GMT+08:00 Greg KH <gregkh@linuxfoundation.org>:
>> > On Thu, Feb 13, 2014 at 12:26:35AM +0800, Barry Song wrote:
>> >> > Well, your 2012 change doesn't seem to be "significant" to warrent a
>> >> > normal copyright update, but the update is usually "less strict" than an
>> >> > original mark, so that might be ok, now that I review these closer.
>> >> >
>> >> > But I'd still prefer to get the opinion of your lawyer about this.
>> >>
>> >> Greg, thanks. i will ask csr lawyer to give some feedback if i can :-)
>> >>
>> >> i am not an expert of  copyright and i am really ignorant on it. in my
>> >> shallow understand, it seems it is difficult to evaluate what is
>> >> "significant" and what is not important as it highly depends on the
>> >> personal opinion? is this something like "there are a thousand Hamlets
>> >> in a thousand people's eyes"?
>> >
>> > It does "depend", but the "general" rule that most everyone follows, and
>> > what I have been advised to stick to, is "1/3 of the file is
>> > modified/added to" by a company/developer.  If that happens, then a
>> > copyright mark is allowed.  That has worked well over the many years of
>> > me having to deal with this, but the issue of "extending" the mark
>> > hasn't really been discussed, so I don't know if that same rule applies
>> > here or not.
>> >
>> > Feedback from your lawyer would be great to have on this, thanks.
>> >
>>
>> Greg, i am inviting our lawyer Cherrie into this, as she is maybe
>> busy, so we might wait some time.
>
> In my research, it's become apparent that the copyright notice should
> just be removed entirely from the files, as they don't mean anything
> from a legal standpoint, so updating them shouldn't really be done
> either, as they don't mean anything.  Although one could argue, if they
> don't mean anything, updating it shouldn't matter, but I don't think
> that the transitive is true here...
>
> It will be interesting to find out what your lawyer says about this.

Greg, all your comments have been forwarded to our layer and counsel.
pls wait for some time :-)

>
> thanks,
>
> greg k-h

-barry

  reply	other threads:[~2014-02-19  5:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 14:08 [PATCH] serial: sirf: update copyright years to 2014 Barry Song
2014-02-12 14:19 ` Greg KH
2014-02-12 14:26   ` Barry Song
2014-02-12 14:37     ` Greg KH
2014-02-12 14:47       ` Barry Song
2014-02-12 16:12         ` Greg KH
2014-02-12 16:26           ` Barry Song
2014-02-12 16:38             ` Greg KH
2014-02-13  2:27               ` Barry Song
2014-02-14 17:14                 ` Greg KH
2014-02-19  5:16                   ` Barry Song [this message]
2014-03-18  2:25                     ` Barry Song
2014-03-18  2:27                       ` Barry Song
2014-03-18  2:33                       ` Greg KH
2014-03-25  2:51                         ` Barry Song
2014-03-25 12:51                           ` Greg KH

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=CAGsJ_4wu80_50Vb4tzBT6Uug+JaSgajdTA6N5fK-FtxvCRxxeQ@mail.gmail.com \
    --to=21cnbao@gmail.com \
    --cc=Baohua.Song@csr.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=workgroup.linux@csr.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.