mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bttv compile failure in 2.5.8-pre2
Date: Mon, 08 Apr 2002 10:49:48 +0200	[thread overview]
Message-ID: <m2elhqy3pv.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <200204062356.g36Nujh03555@vindaloo.ras.ucalgary.ca> <slrnaavu74.t38.kraxel@bytesex.org>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

Gerd Knorr <kraxel@bytesex.org> writes:

> The same is true for nearly all other v4l drivers.  Dave picked up
> my videodev patch from the list and feeded it to Linus, but all the
> related driver fixes are not in the kernel yet ...
>
> 2.4.7 patches are at http://bytesex.org/patches/2.5/
> I'll rediff against -pre2 and resend stuff next days ...

bttv-0.8.x also needs this fix since pointers to __devexit functions
should be marked __devexit_p so that newer binutils don't cry about
references to discarded symbols :


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: in core kernel bttv build fix --]
[-- Type: text/x-patch, Size: 362 bytes --]

--- drivers/media/video/bttv-driver.c.orig	Thu Apr  4 02:12:59 2002
+++ drivers/media/video/bttv-driver.c	Fri Apr  5 06:12:53 2002
@@ -3394,7 +3394,7 @@
         name:     "bttv",
         id_table: bttv_pci_tbl,
         probe:    bttv_probe,
-        remove:   bttv_remove,
+        remove:   __devexit_p(bttv_remove),
 };
 
 static int bttv_init_module(void)

[-- Attachment #3: Type: text/plain, Size: 49 bytes --]


-- 
Still untested beyond 'it compiles' (davej)

      reply	other threads:[~2002-04-08  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 23:56 Richard Gooch
2002-04-07  7:44 ` Gerd Knorr
2002-04-08  8:49   ` Thierry Vignaud [this message]

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=m2elhqy3pv.fsf@vador.mandrakesoft.com \
    --to=tvignaud@mandrakesoft.com \
    --cc=kraxel@bytesex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®