From: Pavel Machek <pavel@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: Thomas Renninger <trenn@suse.de>, Tejun Heo <tj@kernel.org>,
Shem Multinymous <multinymous@gmail.com>,
Elias Oltmanns <eo@nebensachen.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Laptop shock detection and harddisk protection
Date: Tue, 7 Oct 2008 23:40:06 +0200 [thread overview]
Message-ID: <20081007214006.GL6604@elf.ucw.cz> (raw)
In-Reply-To: <20081007211905.GB8151@kroah.com>
> > > If you, or anyone else, writes a new driver from the published
> > > documents, that driver can be accepted. It can not be based on the
> > > existing code written by Shem in any form.
> >
> > Can you detail what "published" means?
>
> Published in a way that has NOTHING to do with these source files.
>
> > Either I can take his sources on sourceforge.net (quite well known
> > place, right) as published information, or I could not use other well
> > known sources such as wikipedia.
>
> If the wikipedia information was written based on these source files,
> no, we can't use that, sorry.
How do I know?
> > Sources on sourceforge.net seem published-enough to me, and if you
> > insist they can't be used, you should provide some reasons...
> >
> > [And no, just calling it "tainted" is not enough.]
>
> {sigh}
>
> Again, for the last time:
> - this code was written by an anonymous person, using documents or
> information that was obtained and used in a manner that was not
> legal according to their employment agreement.
This code is written by anonymous person. He may have used documents
improperly, but I see no signs of that, and don't see why I should
believe you saying so.
If have proof of that, you should talk to sourceforge to take that
code down... or probably their employer should ask sourceforge to do
that.
The documents are on the web from more than year now, on
well-known. That seems to indicate that your theory is not true.
> - because of this, we can not use this code, because we KNOW the
> information was obtained in a improper manner.
Whole wikipedia is written by "anonymous" people. Does that mean that
all information in wikipedia was obtained in a improper manner?
> - so, to get something like this into the kernel, we need to rewrite
> the code, using information obtained LEGALLY from either the
> manufacturer of the chips or computers, or from another TOTALLY
> SEPARATE location.
I'm LEGALLY obtaining the information from sourceforge.net. That is
rather well-known, and non-anonymous source. They continue to publish
this information.
> Does that help explain this?
Unfortunately, no :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-10-07 21:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 16:59 Laptop shock detection and harddisk protection Tejun Heo
2008-09-10 19:43 ` Renato S. Yamane
2008-09-11 10:26 ` Austin Zhang
2008-09-11 11:18 ` Tejun Heo
2008-09-11 16:08 ` Shem Multinymous
2008-09-11 16:34 ` Tejun Heo
2008-08-17 19:48 ` Pavel Machek
2008-09-11 20:00 ` Elias Oltmanns
2008-08-17 19:51 ` Pavel Machek
2008-09-17 15:21 ` Elias Oltmanns
2008-09-17 19:36 ` Shem Multinymous
2008-09-11 20:25 ` Shem Multinymous
2008-08-17 19:30 ` Pavel Machek
2008-09-11 23:35 ` Tejun Heo
2008-09-12 16:59 ` Greg KH
2008-08-17 19:45 ` Pavel Machek
2008-09-17 18:04 ` Greg KH
2008-09-18 11:18 ` Pavel Machek
2008-09-19 9:03 ` Thomas Renninger
2008-09-24 5:14 ` Greg KH
2008-10-07 20:40 ` Pavel Machek
2008-10-07 21:19 ` Greg KH
2008-10-07 21:40 ` Pavel Machek [this message]
2008-10-07 22:03 ` Greg KH
2008-10-07 23:03 ` Pavel Machek
2008-10-07 22:55 ` Shem Multinymous
2008-09-15 8:29 ` Tejun Heo
2008-09-15 18:09 ` Shem Multinymous
2008-09-15 20:10 ` Tejun Heo
2008-09-14 4:41 ` Jeremy Fitzhardinge
2008-09-11 23:36 ` Henrique de Moraes Holschuh
[not found] <baBmH-48R-17@gated-at.bofh.it>
2008-09-12 13:28 ` Bodo Eggert
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=20081007214006.GL6604@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=eo@nebensachen.de \
--cc=greg@kroah.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=multinymous@gmail.com \
--cc=tj@kernel.org \
--cc=trenn@suse.de \
/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).