From: Nicholas Wourms <nwourms@myrealbox.com>
To: linux-kernel@vger.kernel.org
Cc: dri-devel@lists.sourceforge.net
Subject: Re: Update direct-rendering to current DRI CVS tree.
Date: Sun, 30 Mar 2003 09:14:58 -0500 [thread overview]
Message-ID: <3E86FBE2.8080804@myrealbox.com> (raw)
In-Reply-To: 20030330114544.GB16060@suse.de
Dave Jones wrote:
> > #if LINUX_VERSION_CODE <= KERNEL_VERSION(2,4,2)
> > #define down_write down
> > #define up_write up
>
> #if can go, like it did in other parts of the patch.
What will replace it? If you intend to keep the two
projects in sync and easy to update, I'm afraid that it will
call for putting all the later (>=2.4.16) #if's back, as
well as adding gaurds for the current 2.5-specific
scheduling/worqueue changes. Unless, of course, the dri
maintainers are willing to make TRUNK incompatible with
linux-2.4...
Cheers,
Nicholas
next prev parent reply other threads:[~2003-03-30 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200303300712.h2U7CVB32581@hera.kernel.org>
2003-03-30 11:45 ` Update direct-rendering to current DRI CVS tree Dave Jones
2003-03-30 14:14 ` Nicholas Wourms [this message]
2003-03-30 16:55 ` Christoph Hellwig
2003-03-30 17:41 ` Linus Torvalds
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=3E86FBE2.8080804@myrealbox.com \
--to=nwourms@myrealbox.com \
--cc=dri-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox