All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <petr@vmware.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [OT] Re: patch for vmware for Linux-2.6.21
Date: Sun, 13 May 2007 23:15:12 -0700	[thread overview]
Message-ID: <4647FE70.7090700@vmware.com> (raw)
In-Reply-To: <b6a2187b0705132019x579bf28fq5110812432a3b591@mail.gmail.com>

Jeff Chua wrote:
> On 5/14/07, Arjan van de Ven <arjan@infradead.org> wrote:
>> On Mon, 2007-05-14 at 09:18 +0800, Jeff Chua wrote:
> 
>> I'm sorry... but why are you posting these patches here? Those aren't
>> GPL modules, and thus very offtopic for lkml, maybe except for if you
>> want to deliberately have people look at non-gpl code ;(
> 
> I don't like these non-gpl code myself, but it allowed me to use
> Linux-2.6.22 as a base to test the new kvm and hope to migrate to kvm
> soon, and I'm sure some others out there would benefit from it as
> well. I don't claim the code to be perfect, but by releasing to
> others, hopefully someone can tell me where to improve on.

I would strongly recommend you using my patches from 
http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update110.tar.gz. 
  Patch you've created causes memory corruption on 2.6.22-rc1 (and few 
previous kernels, since csum_start got introduced).
					Best regards,
						Petr Vandrovec


  reply	other threads:[~2007-05-14  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  1:18 patch for vmware for Linux-2.6.21 Jeff Chua
2007-05-14  1:35 ` Arjan van de Ven
2007-05-14  3:19   ` Jeff Chua
2007-05-14  6:15     ` Petr Vandrovec [this message]
2007-05-14  6:57     ` Christoph Hellwig

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=4647FE70.7090700@vmware.com \
    --to=petr@vmware.com \
    --cc=jeff.chua.linux@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.