From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: debian developer <debiandev@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 1/4] lockdep: variuos fixes
Date: Tue, 12 Jun 2007 16:08:19 +0200 [thread overview]
Message-ID: <1181657299.7348.327.camel@twins> (raw)
In-Reply-To: <f24d23310706120647n4e125964i3885bd5c340b8903@mail.gmail.com>
On Tue, 2007-06-12 at 19:17 +0530, debian developer wrote:
> On 6/12/07, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > Index: linux-2.6/kernel/lockdep.c
> > ===================================================================
> > --- linux-2.6.orig/kernel/lockdep.c
> > +++ linux-2.6/kernel/lockdep.c
> > @@ -5,7 +5,8 @@
> > *
> > * Started by Ingo Molnar:
> > *
> > - * Copyright (C) 2006 Red Hat, Inc., Ingo Molnar <mingo@redhat.com>
> > + * Copyright (C) 2006,2007 Red Hat, Inc., Ingo Molnar <mingo@redhat.com>
> > + * Copyright (C) 2007 Red Hat, Inc., Peter Zijlstra <pzijlstr@redhat.com>
> > *
> > * this code maps all the lock dependencies as they occur in a live kernel
> > * and will warn about the following classes of locking bugs:
> What exactly is being copyright'ed here?
Thanks for being triply impolite! You score: anonymous, top-posting and
dropping CC-lists.
The code in these files, as in most other files in the Linux kernel, is
copyrighted. The code is Licensed under GPLv2, but copyright belongs to
Red Hat and it's authors are Ingo and myself.
That is, say you want to use this code in a non GPLv2 project (say this
GPLv3 thing) then you would need to contact the copyright owner of this
code.
next prev parent reply other threads:[~2007-06-12 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 12:13 [patch 0/4] lockstat updates Peter Zijlstra
2007-06-12 12:13 ` [patch 1/4] lockdep: variuos fixes Peter Zijlstra
2007-06-12 13:47 ` debian developer
2007-06-12 14:08 ` Peter Zijlstra [this message]
2007-06-12 12:13 ` [patch 2/4] lockdep: fixup sk_callback_lock annotation Peter Zijlstra
2007-06-12 12:13 ` [patch 3/4] lockstat: measure lock bouncing Peter Zijlstra
2007-06-12 12:13 ` [patch 4/4] lockstat: better class name representation Peter Zijlstra
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=1181657299.7348.327.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=debiandev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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