From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Alan Hourihane <alanh@fairlite.demon.co.uk>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/01] New FBDev driver for Intel Vermilion Range
Date: Fri, 06 Apr 2007 06:00:58 +0800 [thread overview]
Message-ID: <1175810458.31131.7.camel@daplas> (raw)
In-Reply-To: <1175809336.10105.54.camel@jetpack.demon.co.uk>
On Thu, 2007-04-05 at 22:42 +0100, Alan Hourihane wrote:
> On Thu, 2007-04-05 at 21:38 +0200, Arnd Bergmann wrote:
> > On Thursday 05 April 2007, Alan Hourihane wrote:
> > > @@ -0,0 +1,405 @@
> > > +/*
> > > + * Copyright (c) Intel Corp. 2007.
> > > + * All Rights Reserved.
> > > + *
> >
> > Saying 'All Rights Reserved' is usually considered the opposite of
> > licensing your code as GPL. I suppose you need to remove that.
>
> Arnd,
>
> Thanks for your comments, and I'll review and make appropriate changes
> as you've suggested.
>
> As for the above, I've noticed that drivers/video/epson1355fb.c also has
> this wording and is under the GPL.
>
"All Rights Reserved" is written notice, a part of copyright law
formality. Nowadays, your works are protected (under the copyright law)
even without that written notice, so the phrase can be excluded.
I don't think the phrase is incompatible with GPL.
Tony
next prev parent reply other threads:[~2007-04-05 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 10:44 [PATCH 01/01] New FBDev driver for Intel Vermilion Range Alan Hourihane
2007-04-05 17:38 ` Valdis.Kletnieks
2007-04-05 18:42 ` James Simmons
2007-04-05 18:58 ` Alan Hourihane
[not found] ` <200704052138.08897.arnd@arndb.de>
2007-04-05 21:42 ` Alan Hourihane
2007-04-05 21:56 ` Arnd Bergmann
2007-04-05 22:00 ` Antonino A. Daplas [this message]
2007-04-06 0:09 ` Antonino A. Daplas
2007-04-06 13:39 ` Alan Hourihane
2007-04-09 20:10 ` Pavel Machek
2007-04-20 9:04 ` Alan Hourihane
2007-04-20 13:51 ` Antonino A. Daplas
2007-04-20 13:54 ` Alan Hourihane
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=1175810458.31131.7.camel@daplas \
--to=adaplas@gmail.com \
--cc=alanh@fairlite.demon.co.uk \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.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