linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 8 Oct 2008 01:03:59 +0200	[thread overview]
Message-ID: <20081007230359.GU6604@elf.ucw.cz> (raw)
In-Reply-To: <20081007220303.GA9066@kroah.com>

Hi!

> > > > 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?
> 
> Unfortunatly, you can't, so don't use it.

Not being able to use wikipedia is little strong, don't you think so?
What's next?

> > 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.
> 
> Yes, I know this is true, for a variety of reasons of what people
> (including the individual in question) told me in private.

Are you saying Shem told you he violated some contracts?

Ok, so can you tell us the details, so that we can evaluate this
ourselves, and (more importantly) so that he can defend himself? He
seems willing to point where specific pieces of code come from.

> And I'm not going to go around asking for code to be taken down, as I'm
> not the one whose contract was invalidated.

Right. So why do you care if this code goes into kernel? Your contract
is not violated, and neither me nor you signed any contract preventing
us from putting that code into kernel.

If you know the details, can you tell us which/whose contract is being
violated here? Maybe we can just get permission of those parties. Or
maybe your information is wrong...

> Ok, once again:
>   - we know this code was created illegally.

If you know this, please share details.

> So can we please just drop this?  Or do you want me to point you at the
> lawyers?

I'll talk to lawyers if I have to. I'd like to understand this.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-10-07 23:02 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
2008-10-07 22:03                           ` Greg KH
2008-10-07 23:03                             ` Pavel Machek [this message]
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=20081007230359.GU6604@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).