From: Valdis.Kletnieks@vt.edu
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andi Kleen <ak@linux.intel.com>,
Huang Ying <ying.huang@intel.com>,
Robert Richter <robert.richter@amd.com>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer
Date: Mon, 27 Apr 2009 12:14:34 -0400 [thread overview]
Message-ID: <49036.1240848874@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 27 Apr 2009 07:44:13 PDT." <alpine.DEB.1.10.0904270738470.9296@makko.or.mcafeemobile.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On Mon, 27 Apr 2009 07:44:13 PDT, Davide Libenzi said:
> IANAL, but what is the point of it? If that's for OSS IP protection
> against Evil Corporate claims, isn't the only fact that you posted the
> code and algorirthm, constitutes Prior Art, that would automatically
> protect your contribution from future claims?
The general idea is that if some Big-Linux-Hating-Company comes to you and says
"You're infringing our patent #XXZZZY in this module", you want to be able pull
out a sheet of paper and say "Yes, and you've shipped 45,348,917 copies of
FooBar Release 7, that infringes on *our* patent #YYXXZ. You probably owe
us more money than we owe you. But we'll let you walk out the door and
never mention it again."
If you're old enough to remember the Cold War, it was called Mutually
Assured Destruction back then. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-04-27 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 9:11 Huang Ying
2009-04-22 9:22 ` Ingo Molnar
2009-04-22 10:16 ` Robert Richter
2009-04-22 10:19 ` Ingo Molnar
2009-04-22 11:35 ` Andi Kleen
2009-04-22 11:30 ` Andi Kleen
2009-04-24 6:06 ` Huang Ying
2009-04-24 10:09 ` Robert Richter
2009-04-24 13:36 ` Steven Rostedt
2009-04-27 7:49 ` Huang Ying
2009-04-27 7:53 ` Andi Kleen
2009-04-27 14:39 ` Steven Rostedt
2009-04-27 14:44 ` Davide Libenzi
2009-04-27 14:57 ` Steven Rostedt
2009-04-27 16:14 ` Valdis.Kletnieks [this message]
2009-04-27 17:05 ` Theodore Tso
2009-04-27 20:06 ` H. Peter Anvin
2009-04-27 14:27 ` Steven Rostedt
2009-04-27 14:36 ` Patenting kernel patches was " Andi Kleen
2009-04-27 14:49 ` Steven Rostedt
2009-04-27 15:33 ` Alan Cox
2009-04-27 0:58 ` Huang Ying
2009-04-22 11:20 ` Andi Kleen
2009-04-22 15:55 ` H. Peter Anvin
2009-04-22 15:58 ` Andi Kleen
2009-04-29 19:15 ` Re-implement MCE log ring buffer as per-CPU ring buffer II Andi Kleen
2009-04-30 7:38 ` 32bit mce unification (Re: Re-implement MCE log ring buffer as per-CPU ring buffer II) Hidetoshi Seto
2009-04-22 11:11 ` Re-implement MCE log ring buffer as per-CPU ring buffer Andi Kleen
2009-04-24 5:51 ` Huang Ying
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=49036.1240848874@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=ak@linux.intel.com \
--cc=davidel@xmailserver.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®