From: tpepper@vato.org
To: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.4.4 breaks VMware
Date: Tue, 1 May 2001 18:42:40 -0700 [thread overview]
Message-ID: <20010501184240.A28442@cb.vato.org> (raw)
Despite VMware's webpage claiming compatibility issues with 2.4.x kernels I'd
been using it without any problem until I upgraded to 2.4.4. I couldn't use
their precompiled modules of course but compiling to match the running kernel
worked fine previously.
This patch replaces a wee bit of code vmware wanted in include/linux/skbuff.h
although I'm guessing it was removed for a reason and vmware should be patched
to use the new method.
--- skbuff.h.orig Tue May 1 18:41:50 2001
+++ skbuff.h Tue May 1 18:41:55 2001
@@ -244,6 +244,11 @@
/* Internal */
#define skb_shinfo(SKB) ((struct skb_shared_info *)((SKB)->end))
+/* for vmware */
+static inline atomic_t *skb_datarefp(struct sk_buff *skb)
+{
+ return (atomic_t *)(skb->end);
+}
/**
* skb_queue_empty - check if a queue is empty
Tim
next reply other threads:[~2001-05-02 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 1:42 tpepper [this message]
2001-05-02 1:52 ` [PATCH] 2.4.4 breaks VMware David S. Miller
2001-05-02 1:56 ` Mohammad A. Haque
2001-05-02 4:53 ` Bjoern A. Zeeb
2001-05-03 1:25 ` Gregory T. Norris
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=20010501184240.A28442@cb.vato.org \
--to=tpepper@vato.org \
--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.