From: Gerd Knorr <kraxel@bytesex.org>
To: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] v4l: videobuf update
Date: Wed, 2 Apr 2003 20:35:44 +0200 [thread overview]
Message-ID: <20030402183544.GA26132@bytesex.org> (raw)
In-Reply-To: <20030402190649.A1091@infradead.org>
> > --- linux-2.5.66/drivers/media/video/video-buf.c 2003-04-02 11:42:51.957723625 +0200
> >
> > +#include <linux/version.h>
>
> Why do you need this?
Because the 2.5.x code doesn't compile on 2.4.x, thus there are version
#ifdefs in my device driver tarballs. You just don't see that because
some perl magic filteres out the 2.4 code when submitting patches for
2.5.x (and visa versa ...). If you fetch the tarballs from bytesex.org
you'll see the #ifdefs in the driver code.
Gerd
--
Michael Moore for president!
next prev parent reply other threads:[~2003-04-02 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 16:36 [patch] v4l: videobuf update Gerd Knorr
2003-04-02 18:06 ` Christoph Hellwig
2003-04-02 18:35 ` Gerd Knorr [this message]
2003-04-02 18:36 ` Christoph Hellwig
2003-04-02 19:19 ` Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 10:52 Gerd Knorr
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=20030402183544.GA26132@bytesex.org \
--to=kraxel@bytesex.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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